Skip to main content
Glama

copy_card

Copy a Trello card with its checklists, labels, attachments, comments, and members into another list or board.

Instructions

Copy a card (with checklists, labels, attachments, comments, members) into a list, possibly on another board.

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": {
      "cardId": "<cardId>",
      "listId": "<listId>"
    },
    "name": "copy_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
posNo
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
cardIdYes
listIdYesDestination list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is covered; the description's real contribution is enumerating exactly what is carried over (checklists, labels, attachments, comments, members), which is genuinely useful for predicting side effects. It omits other behavioral facts an agent might want, such as whether members/comments are re-attributed, permission requirements on the destination list, or name-collision behavior.

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 a compact parenthetical enumerating the copied artifacts; every clause carries information and nothing is redundant.

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 five-parameter mutation with no output schema and 40% schema coverage, the description is thin: three parameters are entirely unexplained and there is no hint about the result (e.g., whether a new card object/id is returned) or about destination-side preconditions. It conveys the essence but leaves too much for the agent to guess.

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?

Schema description coverage is only 40%: listId and lang are documented, while cardId, name, and pos are bare. The description does not compensate — it never explains that cardId is the source card, whether name overrides the copied title, or what pos controls (position string format/placement). Only the destination-list idea is reinforced, which the schema already states.

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?

States a specific verb ('Copy') and resource ('a card') and scopes it precisely ('into a list, possibly on another board'), which cleanly separates it from copy_list and copy_board. It stops short of naming those siblings as alternatives, so it is clear but not fully differentiated in prose.

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 explicit when-to-use or when-not guidance; the agent must infer that this duplicates an existing card rather than building one from scratch (create_card). 'Possibly on another board' hints at the cross-board case but does not state any condition, prerequisite, or alternative.

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