Skip to main content
Glama

List Frames

list_frames

Lists frames in a Figma file with page, ID, name, and size, so you can select a frame ID for layout, style, icon, and render tools.

Instructions

The frames in a Figma file (page, id, name, size). Start here, then pass a frame id to the other tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_url": "<file_url>"
    },
    "name": "list_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full behavioral burden, and it says nothing about access requirements (public vs. private Figma files), whether all pages are enumerated, whether nested frames are included, or pagination limits. The only behavioral hint is the workflow ordering, which is useful but far short of what a no-annotation tool should disclose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the workflow step is placed immediately after the content description. The opening noun fragment is slightly less front-loaded than a verb-first phrasing would be, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and with a single required parameter the surface is small. Still, for the entry point of an entire Figma workflow, missing access/permission expectations leave the definition merely adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter at 0% schema description coverage, and the description only obliquely implies that file_url is a Figma file URL via "The frames in a Figma file." It adds no format, acceptance, or permission detail beyond what the parameter name already suggests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"The frames in a Figma file (page, id, name, size)" identifies the resource and the shape of what comes back, which an agent can distinguish from render_frame or get_layout. The action verb (list) is only implied by the noun phrase, but the intent is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Start here, then pass a frame id to the other tools" gives explicit sequencing: call this first, then feed the returned id into the sibling tools. It stops short of naming which sibling or when-not to use this, but the entry-point role is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.