◎ Discry Score
instagram.com
communication · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
COMMUNICATION · RANK #22 OF 24

Instagram is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Instagram API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 48/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Partial
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Partial
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Partial

Comprehension

55% of score · 53/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Partial
Capability boundariesClear limits — what the API can and cannot do.Partial
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • Instagram API documentation lives within the broader Meta developer portal — an agent searching for 'Instagram API' must navigate through Meta's multi-platform documentation sprawl to find Instagram-specific endpoints
  • Meta provides llms.txt at developers.facebook.com but it covers all Meta platforms (WhatsApp, Marketing API) with minimal Instagram-specific content, reducing its value for agents targeting the Instagram API specifically
  • No official OpenAPI spec is published by Meta — third-party generated specs exist on Versori but are not maintained by the platform team, creating reliability concerns for agent tooling
  • Community MCP servers exist across Smithery, PulseMCP, and Glama but none are official Meta-maintained servers, meaning agents depend on community maintenance for tool integration
  • The robots.txt explicitly allows all crawlers with a broad 'User-agent: * Allow: /' directive, which is permissive for AI access

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Publish an official Instagram Graph API OpenAPI spec maintained alongside the quarterly API version releases
  2. 02Create an Instagram-specific llms.txt that covers the Instagram Platform APIs, scopes, and common workflows separate from the Meta-wide llms.txt
  3. 03Add llms-full.txt with comprehensive Instagram API documentation in markdown for LLM consumption
  4. 04Build or endorse an official Instagram MCP server to replace the fragmented community server ecosystem
  5. 05Add multi-step workflow guides showing common agent patterns: authenticate -> get media -> analyze insights -> moderate comments

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

oauth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

OAuth2 with multiple scope types for different access levels. Graph API versioning (currently v21.0) with quarterly releases. Rate limits documented per-app and per-user. Cursor-based pagination. JSON error responses with error code, subcode, and message. No idempotency support documented.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free