Skip to main content
Glama

figma_read_for_implement

Package selected Figma node structure, preview image, and bitmap assets into outputDir for pixel-level implementation; omit nodeId to use the single selected node.

Instructions

像素级还原打包:结构、预览图、位图资源落到 outputDir。省略 nodeId 时要求恰好选中 1 个节点。

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": {
      "outputDir": "<outputDir>"
    },
    "name": "figma_read_for_implement"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdNo
outputDirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the output artifacts (structure, previews, bitmaps) and that they are written to a directory, implying a filesystem side effect. It does not state whether existing files are overwritten, what happens on failure, or any permission/size considerations.

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 compact sentences, front-loading the output payload before the nodeId precondition. No filler, though the mixed-language phrasing is slightly dense.

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?

For a two-parameter tool with no annotations and no output schema, the description covers what is produced and the key selection precondition. It leaves gaps around overwrite behavior, failure handling, and how the output differs from sibling export/read tools.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: nodeId is explained as optional with a selection-based fallback, and outputDir is described as the destination for the artifact bundle. Both parameters gain meaning not present in the bare minLength schema entries.

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 a specific operation: bundling a pixel-perfect restoration package containing structure, preview images, and bitmap assets, written to outputDir. This is clearly distinct from creation/mutation siblings, though it doesn't explicitly differentiate itself from figma_export_node or figma_get_node_tree, which an agent might reasonably consider alternatives.

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

Usage Guidelines3/5

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

The precondition 'if nodeId is omitted, exactly 1 node must be selected' is a useful usage rule. However, there is no guidance on when to choose this tool over figma_get_node_tree or figma_export_node, and no mention of what the tool does when the selection condition is not met.

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