Skip to main content
Glama

get_instance_overrides

Retrieve override properties from a Figma component instance to apply them to other instances, enabling consistent design updates across your project.

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

  • MCP tool handler that executes the get_instance_overrides logic by forwarding to Figma plugin via sendCommandToFigma and processing the result into a text response.
      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 output structure from the Figma plugin for get_instance_overrides.
    interface getInstanceOverridesResult {
      success: boolean;
      message: string;
      sourceInstanceId: string;
      mainComponentId: string;
      overridesCount: number;
    }
  • MCP server.tool registration for the get_instance_overrides tool, including name, description, input schema, and handler reference.
    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)}`
              }
            ]
          };
        }
      }
    );
  • Zod input schema for the get_instance_overrides tool defining the optional nodeId parameter.
      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?

No annotations are provided, so the description carries the full burden. It describes the tool's function and potential application ('applied to other instances'), but lacks critical behavioral details: whether this is a read-only operation, what permissions are needed, the format of returned overrides, or any rate limits. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded, with two sentences that directly state the tool's purpose and utility. Every sentence adds value: the first defines the action, and the second explains the use case. There's no wasted text, though it could be slightly more structured with bullet points or examples for clarity.

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?

Given the tool's moderate complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and application but lacks details on return values, error handling, or integration with siblings like 'set_instance_overrides.' Without annotations or output schema, the description should do more to compensate, but it meets a bare minimum for understanding.

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%, with the single parameter 'nodeId' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to given the schema's completeness.

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 tool's purpose: 'Get all override properties from a selected component instance.' It specifies the verb ('Get') and resource ('override properties'), and distinguishes it from siblings like 'get_node_info' or 'get_styles' by focusing on component instance 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 by stating 'These overrides can be applied to other instances,' suggesting a workflow context. It doesn't provide explicit when-to-use guidance, alternatives, or exclusions compared to siblings like 'get_node_info' or 'get_styles.' The input schema hints at default behavior (using currently selected instance if no nodeId provided), but the description itself lacks clear usage directives.

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/pipethedev/Talk-to-Figma-MCP'

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