Skip to main content
Glama

set_text_content

Update text content in Figma text nodes by specifying node ID and new text, enabling programmatic text modifications through MCP integration.

Instructions

Set the text content of an existing text node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the text node to modify
textYesNew text content

Implementation Reference

  • Registers the set_text_content MCP tool with name, description, Zod input schema (nodeId, text), and handler function that forwards to Figma plugin.
    server.tool(
      "set_text_content",
      "Set the text content of an existing text node in Figma",
      {
        nodeId: z.string().describe("The ID of the text node to modify"),
        text: z.string().describe("New text content"),
      },
      async ({ nodeId, text }) => {
        try {
          const result = await sendCommandToFigma("set_text_content", {
            nodeId,
            text,
          });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Updated text content of node "${typedResult.name}" to "${text}"`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting text content: ${error instanceof Error ? error.message : String(error)
                  }`,
              },
            ],
          };
        }
      }
    );
  • Handler function sends 'set_text_content' command with nodeId and text to Figma plugin via sendCommandToFigma, processes response or error, returns MCP-formatted content.
    async ({ nodeId, text }) => {
      try {
        const result = await sendCommandToFigma("set_text_content", {
          nodeId,
          text,
        });
        const typedResult = result as { name: string };
        return {
          content: [
            {
              type: "text",
              text: `Updated text content of node "${typedResult.name}" to "${text}"`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting text content: ${error instanceof Error ? error.message : String(error)
                }`,
            },
          ],
        };
      }
    }
  • Input schema using Zod: nodeId (string, ID of text node), text (string, new content).
    {
      nodeId: z.string().describe("The ID of the text node to modify"),
      text: z.string().describe("New text content"),
    },
  • Type definition in FigmaCommand union includes "set_text_content".
    | "scan_text_nodes"
  • TypeScript interface CommandParams defines parameters for set_text_content command: nodeId and text.
    set_text_content: {
      nodeId: string;
      text: string;
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it modifies text content without addressing key behaviors: whether it requires edit permissions, if changes are reversible, what happens to formatting, or error conditions. For a mutation tool, this leaves significant gaps in understanding its operational impact.

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 front-loads the core action and target without any wasted words. It's appropriately sized for a straightforward tool with two parameters.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain return values, error handling, or behavioral nuances like permissions or side effects, leaving the agent with incomplete context for safe invocation.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond implying 'nodeId' refers to an existing text node and 'text' is new content, which the schema already covers. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Set') and target ('text content of an existing text node in Figma'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'set_multiple_text_contents' or 'create_text', which would require a 5.

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 'set_multiple_text_contents' for bulk updates or 'create_text' for new nodes. It mentions 'existing text node' but doesn't clarify prerequisites or exclusions, leaving usage context implied at best.

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