Skip to main content
Glama
andreycretsu

Cursor Talk to Figma MCP

by andreycretsu

get_instance_overrides

Extract override properties from a Figma component instance to apply them to other instances, enabling consistent design updates across multiple elements.

Instructions

Get all override properties from a selected component instance. These overrides can be applied to other instances, which will swap them to match the source component.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdNoOptional ID of the component instance to get overrides from. If not provided, currently selected instance will be used.

Implementation Reference

  • Registration of the 'get_instance_overrides' MCP tool, including Zod input schema, description, and inline handler function that proxies the command to the Figma plugin via sendCommandToFigma.
    server.tool(
      "get_instance_overrides",
      "Get all override properties from a selected component instance. These overrides can be applied to other instances, which will swap them to match the source component.",
      {
        nodeId: z.string().optional().describe("Optional ID of the component instance to get overrides from. If not provided, currently selected instance will be used."),
      },
      async ({ nodeId }) => {
        try {
          const result = await sendCommandToFigma("get_instance_overrides", { 
            instanceNodeId: nodeId || null 
          });
          const typedResult = result as getInstanceOverridesResult;
          
          return {
            content: [
              {
                type: "text",
                text: typedResult.success 
                  ? `Successfully got instance overrides: ${typedResult.message}`
                  : `Failed to get instance overrides: ${typedResult.message}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error copying instance overrides: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • TypeScript interface defining the expected result structure from the Figma plugin for get_instance_overrides.
    interface getInstanceOverridesResult {
      success: boolean;
      message: string;
      sourceInstanceId: string;
      mainComponentId: string;
      overridesCount: number;
    }
  • Handler function for the get_instance_overrides tool. Sends the command to Figma plugin, casts result to typed interface, and formats response content.
    },
    async ({ nodeId }) => {
      try {
        const result = await sendCommandToFigma("get_instance_overrides", { 
          instanceNodeId: nodeId || null 
        });
        const typedResult = result as getInstanceOverridesResult;
        
        return {
          content: [
            {
              type: "text",
              text: typedResult.success 
                ? `Successfully got instance overrides: ${typedResult.message}`
                : `Failed to get instance overrides: ${typedResult.message}`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error copying instance overrides: ${error instanceof Error ? error.message : String(error)}`
            }
          ]
        };
      }
    }
  • Zod schema for input parameters of get_instance_overrides tool.
    {
      nodeId: z.string().optional().describe("Optional ID of the component instance to get overrides from. If not provided, currently selected instance will be used."),
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions that overrides 'can be applied to other instances', which hints at potential use cases, but doesn't disclose critical behavioral traits like whether this is a read-only operation, what permissions are needed, what format the overrides are returned in, or whether there are any rate limits. For a tool with zero annotation coverage, this leaves significant gaps.

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?

The description is appropriately sized with two sentences that each serve a purpose: the first states the core functionality, the second explains potential applications. It's front-loaded with the main purpose. There's minimal waste, though the second sentence could be slightly more concise.

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 annotations and no output schema, the description is incomplete for a tool that presumably returns structured override data. It doesn't explain what format the overrides are returned in, what properties are included, or how to interpret the results. For a tool with zero structured metadata, the description should provide more complete context about the operation and its outputs.

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%, so the schema already fully documents the single optional parameter. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3. It doesn't explain what happens when nodeId is omitted beyond what the schema states.

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 verb 'Get' and resource 'override properties from a selected component instance', making the purpose understandable. It distinguishes from siblings like 'get_node_info' or 'get_styles' by focusing specifically on overrides. However, it doesn't explicitly differentiate from 'set_instance_overrides' beyond the get/set distinction.

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 description implies usage when needing to copy overrides between instances, but doesn't explicitly state when to use this tool versus alternatives like 'get_node_info' or 'get_styles'. It mentions applying overrides to other instances, which provides some context, but lacks clear when-not-to-use guidance or explicit alternative recommendations.

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/andreycretsu/cursor-talk-to-figma-mcp-main'

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