Skip to main content
Glama

create_miro_board

Create Miro boards with learning session content, including frames, sticky notes, and code blocks, for structured technical practice sessions.

Instructions

Create a new Miro board OR add frames to an existing board. This tool uses the Miro REST API to create boards with frames, sticky notes, text, and code blocks. It can create standalone boards or add content to existing boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionContentYesSession content from generate_session output
existingBoardIdNoOptional: ID of an existing Miro board to add frames to. If not provided, creates a new board.

Implementation Reference

  • Zod input validation schema for the create_miro_board tool.
    const CreateMiroBoardInputSchema = z.object({
      sessionContent: z.any(),
      existingBoardId: z.string().optional(),
    });
  • src/index.ts:135-152 (registration)
    Tool metadata registration in ListToolsRequestHandler defining name, description, and input schema.
    {
      name: "create_miro_board",
      description: "Create a new Miro board OR add frames to an existing board. This tool uses the Miro REST API to create boards with frames, sticky notes, text, and code blocks. It can create standalone boards or add content to existing boards.",
      inputSchema: {
        type: "object",
        properties: {
          sessionContent: {
            type: "object",
            description: "Session content from generate_session output",
          },
          existingBoardId: {
            type: "string",
            description: "Optional: ID of an existing Miro board to add frames to. If not provided, creates a new board.",
          },
        },
        required: ["sessionContent"],
      },
    },
  • src/index.ts:244-245 (registration)
    Dispatch registration in CallToolRequestHandler switch statement routing to the handler method.
    case "create_miro_board":
      return await this.createMiroBoard(request.params.arguments);
  • Main handler function that executes the create_miro_board tool logic, handling input validation, Miro integration check, delegation to create or update board, and response formatting.
    private async createMiroBoard(args: any) {
      const input = CreateMiroBoardInputSchema.parse(args);
    
      try {
        if (!this.miroIntegration) {
          throw new Error('Miro integration not initialized. Ensure MIRO_ACCESS_TOKEN is set in the environment.');
        }
    
        let layout;
        if (input.existingBoardId) {
          // Add frames to existing board
          try {
            layout = await this.miroIntegration.addFramesToExistingBoard(input.existingBoardId, input.sessionContent);
          } catch (error) {
            throw new Error(`Failed to add frames to existing board: ${error instanceof Error ? error.message : String(error)}`);
          }
        } else {
          // Create new board
          try {
            layout = await this.miroIntegration.createLearningHourBoard(input.sessionContent);
          } catch (error) {
            throw new Error(`Failed to create new Miro board: ${error instanceof Error ? error.message : String(error)}`);
          }
        }
    
        return {
          content: [
            {
              type: "text",
              text: `✅ Miro board created successfully!`,
            },
            {
              type: "text",
              text: `Board Name: ${input.sessionContent.miroContent.boardTitle}`,
            },
            {
              type: "text",
              text: `Board ID: ${layout.boardId}`,
            },
            {
              type: "text",
              text: `View Link: ${layout.viewLink || 'https://miro.com/app/board/' + layout.boardId}`,
            },
            {
              type: "text",
              text: `\nThe board includes:\n- Overview section with session description\n- Learning objectives\n- 4C activities (Connect, Concept, Concrete, Conclusion)\n- Discussion prompts\n- Key takeaways`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to create Miro board: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Key helper method in MiroIntegration class that orchestrates new board creation, content processing, and layout population (slide or vertical).
    async createLearningHourBoard(sessionContent: SessionContent): Promise<LearningHourMiroLayout> {
      // Post-process content to replace placeholders
      const processedContent = this.contentPostProcessor.processSessionContent(sessionContent);
    
      const boardName = processedContent.miroContent.boardTitle;
      const board = await this.createBoard(boardName, processedContent.sessionOverview);
      const style = processedContent.miroContent.style ?? 'slide';
    
      const layout: LearningHourMiroLayout = {
        boardId: board.id,
        viewLink: board.viewLink,
        sections: {
          overview: {} as MiroFrame,
          objectives: [],
          activities: [],
          discussions: [],
          takeaways: []
        }
      };
    
      if (style === 'slide') {
        return await this.createSlideLayout(board.id, processedContent, layout);
      } else {
        return await this.createVerticalLayout(board.id, processedContent, layout);
      }
    }
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 mentions the tool uses the Miro REST API and can create or add content, but fails to detail critical aspects like required permissions, rate limits, whether changes are reversible, or what the response looks like. This is a significant gap 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in two sentences, front-loaded with the core purpose and followed by implementation details. There is minimal waste, though it could be slightly more concise by integrating the API mention more seamlessly, but overall it earns its place without redundancy.

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 the tool's complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral traits like auth needs or error handling, and while it hints at parameters, it doesn't fully compensate for the lack of structured output information, making it inadequate for safe and effective use by 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 already documents both parameters ('sessionContent' and 'existingBoardId'). The description adds some context by implying 'sessionContent' contains generated content for boards and 'existingBoardId' is optional for adding to existing boards, but it doesn't provide additional syntax or format details beyond what the schema offers, aligning with 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 tool's purpose as creating new Miro boards or adding frames to existing ones, specifying it uses the Miro REST API and can include various content types like sticky notes and code blocks. However, it doesn't explicitly distinguish this from sibling tools like 'delete_miro_board' or 'get_miro_board' in terms of when to use each, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning it can create standalone boards or add to existing ones, but it lacks explicit guidance on when to choose this tool over alternatives like 'list_miro_boards' for viewing or 'delete_miro_board' for removal. No when-not-to-use scenarios or prerequisites are stated, leaving usage context somewhat vague.

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/SDiamante13/learning-hour-mcp'

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