Skip to main content
Glama

archive_card

Archive a Trello card to hide it from the board while preserving its history, attachments, and comments. Reversible if needed.

Instructions

Archive a Trello card (set closed=true). The card is hidden from the board but preserved with its history, attachments and comments. Reversible via unarchive_card. For permanent removal use delete_card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes the exact behavior: sets closed=true, hides the card but preserves history, attachments, and comments. No annotations exist, so description fully covers behavioral traits.

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 concise sentences, front-loaded with the primary action and effect. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (single parameter, no annotations, output schema exists), the description fully covers the operation's context, including reversibility and preservation of content.

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

Parameters4/5

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

Only one parameter 'card_id' with no schema description; however, the tool name and context make its meaning obvious. The description does not add explicit details about the ID format or how to obtain it, but the simplicity mitigates the gap.

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?

Clearly states the action 'Archive a Trello card' and the resource. Differentiates from sibling tools 'delete_card' for permanent removal and 'unarchive_card' for reversal.

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

Usage Guidelines5/5

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

Explicitly provides when to use this tool versus alternatives: 'Reversible via unarchive_card. For permanent removal use delete_card.' Indicates safe, non-destructive usage.

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/scaratec/trellio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server