Skip to main content
Glama
andreycretsu

Cursor Talk to Figma MCP

by andreycretsu

set_annotation

Add or modify annotations on Figma design elements to document requirements, provide feedback, or track changes within the Cursor AI workflow.

Instructions

Create or update an annotation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to annotate
annotationIdNoThe ID of the annotation to update (if updating existing annotation)
labelMarkdownYesThe annotation text in markdown format
categoryIdNoThe ID of the annotation category
propertiesNoAdditional properties for the annotation

Implementation Reference

  • Registration of the MCP tool 'set_annotation' including Zod input schema validation and handler function that forwards the annotation creation/update parameters to the Figma plugin via sendCommandToFigma WebSocket communication.
    server.tool(
      "set_annotation",
      "Create or update an annotation",
      {
        nodeId: z.string().describe("The ID of the node to annotate"),
        annotationId: z.string().optional().describe("The ID of the annotation to update (if updating existing annotation)"),
        labelMarkdown: z.string().describe("The annotation text in markdown format"),
        categoryId: z.string().optional().describe("The ID of the annotation category"),
        properties: z.array(z.object({
          type: z.string()
        })).optional().describe("Additional properties for the annotation")
      },
      async ({ nodeId, annotationId, labelMarkdown, categoryId, properties }) => {
        try {
          const result = await sendCommandToFigma("set_annotation", {
            nodeId,
            annotationId,
            labelMarkdown,
            categoryId,
            properties
          });
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting annotation: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Input schema for the 'set_annotation' tool using Zod for parameter validation: nodeId (required), annotationId (optional), labelMarkdown (required), categoryId (optional), properties (optional array).
    {
      nodeId: z.string().describe("The ID of the node to annotate"),
      annotationId: z.string().optional().describe("The ID of the annotation to update (if updating existing annotation)"),
      labelMarkdown: z.string().describe("The annotation text in markdown format"),
      categoryId: z.string().optional().describe("The ID of the annotation category"),
      properties: z.array(z.object({
        type: z.string()
      })).optional().describe("Additional properties for the annotation")
    },
  • Handler function for 'set_annotation' tool: extracts parameters, calls sendCommandToFigma to execute the annotation operation in the Figma plugin, returns success result or error message in MCP content format.
    async ({ nodeId, annotationId, labelMarkdown, categoryId, properties }) => {
      try {
        const result = await sendCommandToFigma("set_annotation", {
          nodeId,
          annotationId,
          labelMarkdown,
          categoryId,
          properties
        });
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting annotation: ${error instanceof Error ? error.message : String(error)}`
            }
          ]
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create or update' implies a mutation operation, but it doesn't specify permissions needed, whether changes are reversible, rate limits, or what happens when updating versus creating. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for its purpose.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation/update, error conditions, or how to distinguish between create and update scenarios. The agent would need to guess about behavioral aspects and output format.

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 documents all 5 parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, such as explaining the relationship between 'annotationId' for updates versus creates. 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 ('Create or update') and resource ('an annotation'), making the purpose immediately understandable. However, it doesn't differentiate this tool from 'set_multiple_annotations' or 'get_annotations' among its siblings, which would require explicit comparison to achieve a perfect score.

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_annotations' or 'get_annotations'. It lacks any context about prerequisites, appropriate scenarios, or exclusions, leaving the agent to infer usage from the tool name alone.

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