Skip to main content
Glama

create-mindmap-node

Add a mind map node to a Miro board with specified content, position, and optional styling for visual organization.

Instructions

Create a new mind map node on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board where you want to create the node
dataYesThe content and style configuration of the mind map node
positionYesPosition of the node on the board

Implementation Reference

  • The main handler function that implements the tool logic: prepares the mindmap node creation request and calls the Miro API's createMindmapNodesExperimental method.
    fn: async ({ boardId, data, position }) => {
      try {
        // Prepare the request data
        const mindmapCreateRequest = {
          data: {
            nodeView: {
              data: {
                type: "text",
                content: data.content
              }
            },
            ...(data.parentId && { parentId: data.parentId }),
            ...(data.style && { style: data.style })
          },
          position
        };
    
        // Call the Miro API to create a mind map node
        const response = await MiroClient.getApi().createMindmapNodesExperimental(boardId, mindmapCreateRequest);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error creating Miro mind map node: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters: boardId, data (content, parentId, style), and position.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where you want to create the node"),
      data: z.object({
        content: z.string().describe("Text content for the mind map node"),
        parentId: z.string().optional().nullish().describe("ID of the parent node (if this is a child node)"),
        style: z.object({
          fillColor: z.string().optional().nullish().describe("Fill color for the node"),
          textColor: z.string().optional().nullish().describe("Text color for the node")
        }).optional().nullish()
      }).describe("The content and style configuration of the mind map node"),
      position: z.object({
        x: z.number().describe("X coordinate of the node"),
        y: z.number().describe("Y coordinate of the node")
      }).describe("Position of the node on the board")
    },
  • src/index.ts:186-186 (registration)
    Registers the createMindmapNodeTool with the ToolBootstrapper server.
    .register(createMindmapNodeTool)
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 tool but doesn't mention whether it requires specific permissions, if it's idempotent, what happens on failure, or what the return value looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a tool with comprehensive schema documentation and follows a clear subject-verb-object structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 3 required parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context, usage guidance, and output information. The schema handles parameter documentation well, but the description doesn't compensate for the missing annotations and output schema.

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 schema description coverage is 100%, so all parameters are documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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') and resource ('new mind map node on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create-text-item' or 'create-sticky-note-item' that also create items on Miro boards, missing the specific mind map node 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 doesn't mention prerequisites (e.g., needing an existing board), compare to similar creation tools in the sibling list, or indicate when other tools might be more appropriate for different types of content creation.

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