Skip to main content
Glama
Sign In
Claude Talk to Figma MCP

Claude Talk to Figma MCP

by arinspunk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_image_from_node

Extract image metadata from a Figma node via node ID. Access image properties for design analysis and automation.

Instructions

Extract image metadata from a node

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": {
      "nodeId": "<nodeId>"
    },
    "name": "get_image_from_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to get image from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'extract image metadata' without detailing what metadata is returned, behavior on non-image nodes, or error conditions. Inadequate for unannotated tool.

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

Conciseness5/5

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

Single sentence is extremely concise and front-loaded with the core action. No wasted words.

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?

Given no output schema and only one parameter, description should specify what 'image metadata' includes (e.g., dimensions, format). Current description leaves ambiguity, making it incomplete for effective tool use.

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?

Schema description coverage is 100% (nodeId described as 'The ID of the node'). Description adds no additional parameter semantics beyond schema, so baseline score of 3 is appropriate.

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

Purpose5/5

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

Description uses specific verb 'Extract' and resource 'image metadata from a node', clearly distinguishing from sibling tools like 'export_node_as_image' or 'get_svg' which handle actual image data.

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?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of prerequisites, context, or exclusion cases.

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

Deploy Server

Other Tools