Skip to main content
Glama

create-text-item

Add text content to a Miro board by specifying position, style, and dimensions for visual collaboration.

Instructions

Create a new text item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board where the text will be created
dataYesThe content of the text item
positionYesPosition of the text item on the board
geometryNoDimensions of the text item
styleNoStyle configuration of the text item

Implementation Reference

  • The handler function that implements the logic to create a text item on a Miro board using the Miro API client.
    fn: async ({ boardId, data, position, geometry, style }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new TextCreateRequest();
        
        const textData = new TextData();
        textData.content = data.content;
        
        createRequest.data = textData;
        createRequest.position = position;
        
        if (geometry) {
          createRequest.geometry = geometry;
        }
        
        if (style) {
          createRequest.style = style;
        }
    
        const result = await MiroClient.getApi().createTextItem(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod-based input schema defining parameters for the create-text-item tool: boardId, data.content, position, optional geometry.width, and style properties.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where the text will be created"),
      data: z.object({
        content: z.string().describe("Text content of the text item")
      }).describe("The content of the text item"),
      position: z.object({
        x: z.number().describe("X coordinate of the text item"),
        y: z.number().describe("Y coordinate of the text item")
      }).describe("Position of the text item on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Width of the text item")
      }).optional().nullish().describe("Dimensions of the text item"),
      style: z.object({
        color: z.string().optional().nullish().describe("Color of the text"),
        fontSize: z.number().optional().nullish().describe("Font size of the text"),
        textAlign: z.string().optional().nullish().describe("Alignment of the text (left, center, right)")
      }).optional().nullish().describe("Style configuration of the text item")
    },
  • src/index.ts:146-146 (registration)
    Registers the createTextItemTool (create-text-item) with the ToolBootstrapper instance in the main index file.
    .register(createTextItemTool)
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 but doesn't mention any behavioral aspects like required permissions, whether it's idempotent, what happens on duplicate creation, error conditions, or what the return value contains. For a mutation tool with zero annotation coverage, this leaves significant 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, clear sentence that efficiently communicates the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 creation tool with 5 parameters (including nested objects), no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation, what the tool returns, error handling, or contextual constraints. The description should provide more complete guidance for proper tool invocation.

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%, meaning all parameters are well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 text item') and the resource ('on a Miro board'), making the purpose specific and understandable. However, it doesn't explicitly differentiate this tool from other creation tools like create-sticky-note-item or create-card-item, which would require mentioning the specific type of item being created.

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. With many sibling tools for creating different item types (e.g., create-sticky-note-item, create-card-item), there's no indication that this is specifically for plain text items or when text items are preferred over other formats.

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