Skip to main content
Glama

copy_board

Duplicate a Trello board and optionally copy its cards to create a matching board for backups, templates, or project reuse.

Instructions

Copy a board. With includeCards=true (default) the cards are copied too.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boardId": "<boardId>",
      "name": "<name>"
    },
    "name": "copy_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameYes
boardIdYes
includeCardsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is known. The description adds real value by disclosing that cards are copied by default (includeCards=true), but it omits what else is or is not carried over (lists, labels, members, attachments) and whether the source board is untouched.

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?

Two short sentences, purpose front-loaded, with the non-obvious default immediately following. No filler; every clause carries 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 mutation tool with no output schema and low schema coverage, the description should say what the result is (new board id?), where the copy is created, and what fidelity the copy has. None of that is present, leaving the agent under-informed before invoking a write operation.

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 coverage is only 25% (only 'lang' is documented), so the description must compensate. It does explain includeCards' meaning and default, but leaves boardId (source vs target) and name (new board name?) unstated, so the two required parameters remain semantically ambiguous.

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?

"Copy a board" is a specific verb plus resource, and the resource (board vs card/list) implicitly separates it from siblings like copy_card and copy_list. It stops short of explicitly routing the agent away from those siblings, so it is clear but not fully differentiated.

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?

There is no guidance on when to choose this over copy_card/copy_list/create_board, no prerequisites, and no note on where the copy lands or what permissions are needed. The only conditional information is the includeCards default, which is behavioral rather than usage-scoping.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.