Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

get_remote_components

Retrieve available components from team libraries in Figma to access shared design elements for AI-assisted design workflows.

Instructions

Get available components from team libraries in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_remote_components' MCP tool. It sends a 'get_remote_components' command to the Figma plugin via WebSocket, formats the result as JSON text content, and handles errors.
    server.tool(
      "get_remote_components",
      "Get available components from team libraries in Figma",
      {},
      async () => {
        try {
          const result = await sendCommandToFigma("get_remote_components");
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting remote components: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Registers the 'get_remote_components' tool on the MCP server within the registerDocumentTools function.
    server.tool(
      "get_remote_components",
      "Get available components from team libraries in Figma",
      {},
      async () => {
        try {
          const result = await sendCommandToFigma("get_remote_components");
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting remote components: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Includes 'get_remote_components' in the FigmaCommand type union, used for typing commands sent to the Figma plugin.
    | "get_remote_components"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves components but does not describe what 'available' means, whether it includes pagination, rate limits, or error conditions, or how the data is returned. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for a simple tool, with zero waste.

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 the lack of annotations and output schema, the description is incomplete. It does not explain what the return value looks like (e.g., list of components, metadata), potential errors, or behavioral traits. For a tool that likely returns data, more context on output format or usage constraints would improve completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it could hint at implicit parameters like authentication or filtering, though not required. Baseline 4 is given as it compensates adequately for the lack of parameters.

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 clearly states the action ('Get') and resource ('available components from team libraries in Figma'), providing a specific purpose. It distinguishes from sibling tools like 'get_local_components' by specifying 'remote' components from 'team libraries', though it could be more explicit about the distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_local_components' or other sibling tools. It lacks context on prerequisites, such as whether authentication or specific permissions are needed, or when this tool is appropriate in a workflow.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arinspunk/claude-talk-to-figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server