◎ Discry Score
figma.com
devtools · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 96 (A)
Discry your API →
DEVTOOLS · RANK #32 OF 39

Figma is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Figma 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 · 38/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
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.Fail
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 74/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Pass
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.Partial

What we found

  • Figma explicitly BLOCKS all major AI bots in robots.txt (GPTBot, anthropic-ai, CCBot, Google-Extended, cohere-ai) — the most aggressive AI-blocking stance in this batch
  • Despite blocking AI crawlers, Figma maintains an official OpenAPI spec at github.com/figma/rest-api-spec and an official MCP server guide
  • 57+ community Figma MCP servers exist across registries, making it one of the most MCP-saturated APIs despite the blocking
  • Figma provides community-resources/agent_skills on GitHub showing awareness of agentic use cases
  • The contradiction between blocking AI crawlers and actively supporting MCP/agent tooling suggests a deliberate strategy of controlled access

What to change

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

  1. 01Consider allowing AI bots access to developer documentation pages in robots.txt while blocking other content
  2. 02Add llms.txt focused on the REST API and Plugin API for agent consumption
  3. 03Create an official AGENTS.md in the figma GitHub org linking to the MCP server guide
  4. 04Add .well-known/mcp.json pointing to the official Figma MCP server
  5. 05Add llms-full.txt with complete API documentation in markdown

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.

OAuth2personal access token✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Figma uses OAuth2 and personal access tokens. JSON error responses. Rate limits documented. Cursor-based pagination for large datasets.

See your own Discry Score.

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

Discry your API — free