Atlassian Trello MCP Server

trello_archive_card

Archive or unarchive a Trello card by providing its ID and setting a boolean value.

Instructions

Archive or unarchive a Trello card. Set value to true to archive, false to unarchive.

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>",
      "value": "<value>"
    },
    "name": "trello_archive_card"
  }
}

Input Schema

Name	Required	Description
`apiKey`	No	Trello API key (optional if TRELLO_API_KEY env var is set)
`token`	No	Trello API token (optional if TRELLO_TOKEN env var is set)
`cardId`	Yes	ID or URL of the card to archive/unarchive (e.g. "abc123" or "https://trello.com/c/abc123/1-title")
`value`	Yes	true to archive, false to unarchive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It only states the toggle action but omits side effects, permissions, rate limits, or what archiving means for the card's visibility.

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 only two sentences, front-loaded with the action, and every word carries meaning with no waste.

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

Completeness4/5

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

For a simple toggle action with no output schema, the description covers the essential behavior. However, it lacks information about the return value or any confirmation of the action's success.

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 100% with descriptions, so the description adds little extra meaning beyond clarifying the boolean value parameter's effect. The baseline is 3 since the schema already does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it archives or unarchives a card, with a specific verb and resource, and the boolean toggling distinguishes it from other card manipulation tools like move_card or update_card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the function but does not provide any guidance on when to use this tool versus other card-related tools, nor does it mention prerequisites or exclusions.

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

Deploy Server