Skip to main content
Glama

create-connector

Create visual connections between items on a Miro board by specifying start and end points, enabling diagram creation and relationship mapping.

Instructions

Create a new connector between items on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board where the connector will be created
startItemYesStart item of the connector
endItemYesEnd item of the connector
styleNoStyle configuration of the connector

Implementation Reference

  • The handler function that implements the core logic of the 'create-connector' tool. It validates inputs, constructs a ConnectorCreationData object, and calls the Miro API to create the connector on the specified board.
    fn: async ({ boardId, startItem, endItem, style }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        const connectorData = new ConnectorCreationData();
        connectorData.startItem = startItem;
        connectorData.endItem = endItem;
        
        if (style) {
          connectorData.style = style;
        }
    
        const result = await MiroClient.getApi().createConnector(boardId, connectorData);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The Zod-based input schema defining the parameters for the 'create-connector' tool, including boardId, startItem, endItem, and optional style.
    name: "create-connector",
    description: "Create a new connector between items on a Miro board",
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where the connector will be created"),
      startItem: z.object({
        id: z.string().describe("ID of the item at the start of the connector")
      }).describe("Start item of the connector"),
      endItem: z.object({
        id: z.string().describe("ID of the item at the end of the connector") 
      }).describe("End item of the connector"),
      style: z.object({
        strokeColor: z.string().optional().nullish().describe("Color of the connector stroke"),
        strokeWidth: z.number().optional().nullish().describe("Width of the connector stroke"),
        strokeStyle: z.string().optional().nullish().describe("Style of the connector stroke (normal, dashed, etc.)"),
        startStrokeCap: z.string().optional().nullish().describe("Start stroke cap style"),
        endStrokeCap: z.string().optional().nullish().describe("End stroke cap style")
      }).optional().nullish().describe("Style configuration of the connector")
    },
  • src/index.ts:129-129 (registration)
    Registers the createConnectorTool ("create-connector") with the ToolBootstrapper instance.
    .register(createConnectorTool)
  • src/index.ts:28-28 (registration)
    Imports the createConnectorTool module for registration.
    import createConnectorTool from './tools/createConnector.js';
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. It states this is a creation operation (implying mutation/write), but doesn't mention permission requirements, whether the connector appears immediately on the board, if there are rate limits, or what happens if the start/end items don't exist. The description lacks crucial behavioral context for a write operation.

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, clear sentence with zero wasted words. It's appropriately sized for a creation tool and front-loads the essential information. Every word earns its place in conveying the core functionality.

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 what a successful creation returns (e.g., connector ID), error responses, or the visual/functional impact on the Miro board. Given the complexity of creating graphical connectors between items, more context about the operation's effects is needed.

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 4 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., that startItem and endItem must be valid existing items) or provide examples of style configurations. 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 a new connector') and the resource ('between items on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update-connector' or explain what a 'connector' represents in the Miro context (e.g., a line/arrow between objects).

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 'update-connector' or 'create-items-in-bulk' (which might include connectors). There's no mention of prerequisites (e.g., existing items on the board), error conditions, or typical use cases for creating connectors in Miro workflows.

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/k-jarzyna/mcp-miro'

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