Skip to main content
Glama
andreycretsu

Cursor Talk to Figma MCP

by andreycretsu

set_default_connector

Set a copied connector node as the default connector in Figma to streamline design automation through Cursor AI communication.

Instructions

Set a copied connector node as the default connector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectorIdNoThe ID of the connector node to set as default

Implementation Reference

  • MCP tool registration for 'set_default_connector'. Includes inline input schema (optional connectorId string) and handler function that proxies the command to the Figma plugin via sendCommandToFigma for execution.
      "set_default_connector",
      "Set a copied connector node as the default connector",
      {
        connectorId: z.string().optional().describe("The ID of the connector node to set as default")
      },
      async ({ connectorId }) => {
        try {
          const result = await sendCommandToFigma("set_default_connector", {
            connectorId
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Default connector set: ${JSON.stringify(result)}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting default connector: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Zod schema definition for the tool's input parameters: optional connectorId (string).
      connectorId: z.string().optional().describe("The ID of the connector node to set as default")
    },
  • Handler function for the tool: sends 'set_default_connector' command with connectorId to Figma plugin via websocket proxy, returns success/error text content.
      try {
        const result = await sendCommandToFigma("set_default_connector", {
          connectorId
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Default connector set: ${JSON.stringify(result)}`
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting default connector: ${error instanceof Error ? error.message : String(error)}`
            }
          ]
        };
      }
    }
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 sets a default connector, implying a mutation operation, but doesn't cover critical aspects like required permissions, whether this action is reversible, potential side effects, or error conditions. This is a significant gap for a tool that likely modifies system state.

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, direct sentence that efficiently conveys the core action without unnecessary words. It's front-loaded with the key verb and resource, making it easy to parse and understand quickly, which is ideal for conciseness.

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 tool likely performs a mutation (setting a default connector) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, or return values, making it inadequate for safe and effective use by an AI agent in a design or connector management context.

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?

The input schema has 100% description coverage, with 'connectorId' clearly documented. The description adds no additional parameter semantics 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 detract.

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 resource ('a copied connector node as the default connector'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'create_connections' or 'move_node', which might also involve connector operations, leaving some ambiguity about its unique role.

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. It doesn't mention prerequisites (e.g., needing a copied connector node), exclusions, or related tools like 'create_connections' for creating connectors, leaving the agent to infer usage context 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