Skip to main content
Glama

update-connector

Modify existing connectors on Miro boards by updating their endpoints, stroke styles, colors, or connection points to reflect changes in visual diagrams.

Instructions

Update an existing connector on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the connector
connectorIdYesUnique identifier (ID) of the connector that you want to update
startItemNoStart item of the connector
endItemNoEnd item of the connector
styleNoUpdated style configuration of the connector

Implementation Reference

  • Handler function that updates a connector on a Miro board by constructing ConnectorChangesData and calling MiroClient.updateConnector.
    fn: async ({ boardId, connectorId, startItem, endItem, style }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!connectorId) {
          return ServerResponse.error("Connector ID is required");
        }
    
        const changes = new ConnectorChangesData();
        
        if (startItem) {
          changes.startItem = startItem;
        }
        
        if (endItem) {
          changes.endItem = endItem;
        }
        
        if (style) {
          changes.style = style;
        }
    
        const result = await MiroClient.getApi().updateConnector(boardId, connectorId, changes);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters for the update-connector tool.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that contains the connector"),
      connectorId: z.string().describe("Unique identifier (ID) of the connector that you want to update"),
      startItem: z.object({
        id: z.string().describe("ID of the item at the start of the connector")
      }).optional().nullish().describe("Start item of the connector"),
      endItem: z.object({
        id: z.string().describe("ID of the item at the end of the connector")
      }).optional().nullish().describe("End item of the connector"),
      style: z.object({
        strokeColor: z.string().optional().nullish().describe("Updated color of the connector stroke"),
        strokeWidth: z.number().optional().nullish().describe("Updated width of the connector stroke"),
        strokeStyle: z.string().optional().nullish().describe("Updated style of the connector stroke (normal, dashed, etc.)"),
        startStrokeCap: z.string().optional().nullish().describe("Updated start stroke cap style"),
        endStrokeCap: z.string().optional().nullish().describe("Updated end stroke cap style")
      }).optional().nullish().describe("Updated style configuration of the connector")
    },
  • src/index.ts:31-31 (registration)
    Import statement for the updateConnectorTool.
    import updateConnectorTool from './tools/updateConnector.js';
  • src/index.ts:132-132 (registration)
    Registration of the update-connector tool using ToolBootstrapper.register method.
    .register(updateConnectorTool)
Behavior2/5

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

With no annotations, the description carries full burden but only states it's an update operation without disclosing behavioral traits. It doesn't mention permissions required, whether changes are reversible, rate limits, or what happens if parameters are omitted (e.g., partial updates). 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 waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 incomplete. It lacks behavioral context, usage guidelines, and doesn't compensate for the absence of structured safety or output information, leaving significant gaps for an AI agent.

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 fully documents all 5 parameters. The description adds no meaning beyond what the schema provides, not explaining parameter interactions or update semantics. 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 ('Update') and resource ('an existing connector on a Miro board'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'update-board' or 'update-card-item' by specifying what aspects of a connector can be updated (e.g., endpoints, style).

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing board and connector IDs), exclusions, or related tools like 'create-connector' or 'delete-connector' from the sibling list.

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