Skip to main content
Glama

set_default_connector

Set a copied connector node as the default connector in Figma to maintain consistent styling across designs.

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

  • Handler function that forwards the set_default_connector command to the Figma plugin server via sendCommandToFigma, handling success and error responses with appropriate content blocks.
      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 defining the input parameters for the tool: optional connectorId string.
      connectorId: z.string().optional().describe("The ID of the connector node to set as default")
    },
    async ({ connectorId }) => {
  • MCP tool registration using server.tool(), including name, description, schema, and handler function.
      "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)}`
              }
            ]
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Set') but does not specify permissions, side effects, or response behavior. This is inadequate for a tool that likely changes system state without any safety or operational context.

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 waste, clearly front-loading the core action. It is appropriately sized for a simple tool, making it highly concise and well-structured.

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. It fails to address key aspects like what 'default connector' means, potential impacts, or return values, which are crucial for a mutation tool in a design context with many siblings.

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 input schema fully documents the 'connectorId' parameter. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 'Set' and the resource 'a copied connector node as the default connector', making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'create_connections' or 'move_node', which might involve connectors, so it misses full sibling distinction.

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 lacks context on prerequisites (e.g., needing a copied connector node), exclusions, or comparisons to sibling tools like 'create_connections', leaving usage unclear.

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