Skip to main content
Glama

Export Icons

export_icons

Exports all icons in a Figma frame as inline SVG keyed by icon name, enabling direct paste into a web page.

Instructions

Every icon in the frame as inline SVG, keyed by the icon's name. Paste them into the page as-is.

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>",
      "frame_id": "<frame_id>"
    },
    "name": "export_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes
frame_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load: it usefully discloses the return format (inline SVG, name-keyed) which implies a read-only extraction. It says nothing about permissions, size limits, behavior for frames with no icons, or nested component icons, so the burden is only partly met.

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 tight sentences with the payload described first and the usage hint second; no filler. The trailing imperative is slightly ambiguous about who pastes where, but the text is efficiently sized.

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

Completeness2/5

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

An output schema exists, which covers return values, but the total absence of parameter documentation for a two-required-param tool leaves a real gap, and nothing explains scoping (e.g., whether nested frames are traversed). For a tool requiring a file URL and frame ID, this is under-specified.

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

Parameters2/5

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

Both required parameters (file_url, frame_id) have 0% schema description coverage, and the description never mentions them. The agent gets no clarification of URL vs. file key format or how frame_id is obtained, so it fails to compensate for the coverage gap.

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 description names the specific resource (every icon in the frame) and the exact output shape (inline SVG keyed by the icon's name), so the agent knows what it gets. The action verb is only implicit from the tool name/writeup, and it never distinguishes itself from siblings like render_frame or get_layout.

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

Usage Guidelines2/5

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

"Paste them into the page as-is" hints at a downstream use, but there is no statement of when to pick this over render_frame or get_layout, and no prerequisites or exclusions. The agent must infer the routing decision entirely.

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