Skip to main content
Glama

copy_list

Copy a Trello list and all its cards to the same or another board by specifying the source list and destination board.

Instructions

Copy a list with all its cards onto a board (the same or another one).

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": {
      "listId": "<listId>",
      "boardId": "<boardId>"
    },
    "name": "copy_list"
  }
}

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.
nameNo
listIdYes
boardIdYesDestination board

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-destructive, open-world write operation, so the safety profile is covered. The description adds one genuinely non-obvious behavioral fact: child cards are duplicated along with the list. It says nothing about where the new list lands, how its name defaults, or what happens to labels/attachments/checklists on the copied cards.

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?

A single front-loaded sentence with no filler; the cascade behavior ('with all its cards') appears before the destination clause. Nothing in it is redundant with the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with no output schema, the definition covers the core behavior but leaves the agent guessing about the new list's resulting name/position and the two undocumented parameters. With annotations handling safety and no return value to explain, it lands at adequate-but-thin rather than inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only boardId carries a schema description ('Destination board'), so coverage is 50% and the description must compensate. 'Copy a list ... onto a board' weakly implies listId is the source, but the optional 'name' parameter is left entirely unexplained (new list's name? ignored?) and 'lang' is never acknowledged.

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?

Specific verb ('Copy') plus resource ('a list') plus an explicit scope ('with all its cards') that implicitly separates it from copy_card and copy_board. It never names a sibling outright, so differentiation is achieved through the object scope rather than by routing language.

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?

No when-to-use guidance, no prerequisites (write access to the destination board), and no mention of when copying a whole list is preferable to copying cards individually with copy_card. The only conditional present, 'the same or another one', describes the destination, not tool selection.

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