Skip to main content
Glama
deenesjakoruzh
k-jarzyna

Miro MCP

by k-jarzyna
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

copy-board

Duplicate Miro boards to create new versions with custom names, descriptions, sharing policies, or team assignments.

Instructions

Create a copy of an existing Miro board with optional new settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copyFromYesUnique identifier (ID) of the board that you want to copy
nameNoName for the new copied board
descriptionNoDescription for the new copied board
sharingPolicyNoSharing policy for the new copied board
teamIdNoTeam ID to assign the new copied board to

Implementation Reference

  • src/tools/copyBoard.ts:16-35 (handler)
    The asynchronous function that implements the core logic of the 'copy-board' tool. It validates the required 'copyFrom' parameter, constructs optional changes for the new board, calls the Miro API to copy the board, and returns a formatted JSON response or an error.
    fn: async ({ copyFrom, name, description, sharingPolicy, teamId }) => {
  try {
    if (!copyFrom) {
      return ServerResponse.error("Source board ID is required");
    }

    const copyBoardChanges = {};
    if (name) copyBoardChanges['name'] = name;
    if (description !== undefined) copyBoardChanges['description'] = description;
    if (sharingPolicy) copyBoardChanges['sharingPolicy'] = { access: sharingPolicy };
    if (teamId) copyBoardChanges['teamId'] = teamId;

    const boardData = await MiroClient.getApi().copyBoard(copyFrom, copyBoardChanges);

    return ServerResponse.text(JSON.stringify(boardData, null, 2));
  } catch (error) {
    process.stderr.write(`Error copying Miro board: ${error}\n`);
    return ServerResponse.error(error);
  }
}
  • src/tools/copyBoard.ts:6-15 (schema)
    Defines the ToolSchema for the 'copy-board' tool, including the name, description, and Zod-based input schema for the tool parameters.
    const copyBoardTool: ToolSchema = {
  name: "copy-board",
  description: "Create a copy of an existing Miro board with optional new settings",
  args: {
    copyFrom: z.string().describe("Unique identifier (ID) of the board that you want to copy"),
    name: z.string().optional().nullish().describe("Name for the new copied board"),
    description: z.string().optional().nullish().describe("Description for the new copied board"),
    sharingPolicy: z.enum(['private', 'view', 'comment', 'edit']).optional().nullish().describe("Sharing policy for the new copied board"),
    teamId: z.string().optional().nullish().describe("Team ID to assign the new copied board to")
  },
  • src/index.ts:115-115 (registration)
    Registers the copyBoardTool instance with the ToolBootstrapper in the main server bootstrap process.
    .register(copyBoardTool)

Tool Definition Quality

C2.9/5.0
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 the tool creates a copy but doesn't reveal whether this is a read-only or destructive operation, what permissions are required, whether it preserves all board content, or what happens to the original board. The mention of 'optional new settings' hints at customization but lacks specifics about default behaviors or limitations. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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 immediately conveys the core functionality. Every word earns its place: 'Create a copy' establishes the action, 'existing Miro board' specifies the resource, and 'optional new settings' hints at customization without unnecessary elaboration. There's no redundant information or verbose explanations, making it optimally concise while still being informative.

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 tool that creates a new board copy (a mutation operation) with 5 parameters and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., the new board ID, success status, or error conditions), doesn't address permission requirements, and provides minimal behavioral context. While the schema covers parameters well, the description fails to compensate for the lack of annotations and output schema, leaving the agent with incomplete understanding of how to properly use this tool.

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 all 5 parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'optional new settings' which loosely corresponds to parameters like name, description, sharingPolicy, and teamId. However, it doesn't provide additional context about parameter relationships, default values, or practical usage examples that would enhance understanding beyond the structured schema.

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 copy') and resource ('existing Miro board'), making the purpose immediately understandable. It distinguishes itself from 'create-board' by specifying it copies an existing board rather than creating a new one from scratch. However, it doesn't explicitly differentiate from other board-related tools like 'update-board' or 'get-specific-board' in terms of when to choose copying over other operations.

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 like 'create-board' for starting fresh or 'update-board' for modifying existing boards. It mentions 'optional new settings' but doesn't clarify what scenarios warrant copying versus direct creation or modification. There's no mention of prerequisites, permissions needed, or typical use cases for board duplication.

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