Skip to main content
Glama

create-board

Create a new Miro board with custom name, description, sharing permissions, and team assignment.

Instructions

Create a new Miro board with specified name and sharing policies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the board to create
descriptionNoDescription of the board
sharingPolicyNoSharing policy for the board
teamIdNoTeam ID to assign the board to

Implementation Reference

  • The asynchronous handler function that executes the core logic of the 'create-board' tool. It validates the board name, constructs board changes including sharing policy, calls MiroClient.getApi().createBoard(), and returns the board data or an error response.
    fn: async ({ name, description, sharingPolicy, teamId }) => {
      try {
        if (!name) {
          return ServerResponse.error("Board name is required");
        }
    
        const boardChanges = {
          name,
          description,
          sharingPolicy: {
            access: sharingPolicy || 'private'
          },
          teamId
        };
    
        const boardData = await MiroClient.getApi().createBoard(boardChanges);
    
        return ServerResponse.text(JSON.stringify(boardData, null, 2));
      } catch (error) {
        process.stderr.write(`Error creating Miro board: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including the tool name, description, and Zod-based input schema for parameters: name (required string), description (optional), sharingPolicy (optional enum), teamId (optional).
    const createBoardTool: ToolSchema = {
      name: "create-board",
      description: "Create a new Miro board with specified name and sharing policies",
      args: {
        name: z.string().describe("Name of the board to create"),
        description: z.string().optional().nullish().describe("Description of the board"),
        sharingPolicy: z.enum(['private', 'view', 'comment', 'edit']).optional().nullish().describe("Sharing policy for the board"),
        teamId: z.string().optional().nullish().describe("Team ID to assign the board to")
      },
  • src/index.ts:112-112 (registration)
    Registers the createBoardTool with the ToolBootstrapper instance in the main server entry point.
    .register(createBoardTool)
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 states the tool creates a board but lacks details on permissions required, whether it's idempotent, rate limits, or what happens on failure (e.g., if the name is duplicate). This leaves significant gaps for a mutation tool.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and includes key parameters, making it easy to parse quickly.

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 complexity of a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., board ID or success status), error conditions, or behavioral nuances, leaving the agent with incomplete operational context.

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 parameters. The description mentions 'name and sharing policies', which aligns with the schema but adds no extra meaning beyond it, such as default values or constraints not in the schema. This meets the baseline for high schema 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 action ('Create a new Miro board') and specifies key resources ('with specified name and sharing policies'), making the purpose evident. However, it doesn't explicitly distinguish this tool from similar siblings like 'copy-board' or 'update-board', which would require mentioning unique aspects like initial creation versus modification or duplication.

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 a team ID for certain contexts), exclusions, or comparisons to sibling tools like 'copy-board' or 'update-board', leaving the agent without usage context.

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