Trello MCP Server

close_board

Archive a Trello board to keep your workspace organized, with the option to reopen it later if needed.

Instructions

Archive un board Trello (réversible, peut être réouvert)

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": "close_board"
  }
}

Input Schema

Name	Required	Description	Default
`boardId`	Yes	Parameter boardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the key behavioral trait that archiving is reversible and reopenable, which is valuable. However, it does not describe side effects on board contents, visibility changes, permissions required, or the nature of the response.

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 concise sentence with no filler. The primary action is front-loaded, and the reversibility caveat is efficiently placed in parentheses.

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 one-parameter mutation with no output schema, the description is largely sufficient. It names the action, identifies the resource, and clarifies reversibility. It could be more complete by explicitly contrasting with delete_board or mentioning effects on cards/lists, but these are not critical gaps.

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 description coverage is 100%, so the baseline is 3. The description does not add any meaning beyond the schema; the parameter description is minimal ('24 characters') but present.

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?

The description clearly states the action 'Archiver' on the resource 'board Trello', which is specific and distinguishable from destructive operations like delete_board. The parenthetical 'réversible, peut être réouvert' reinforces that this is not permanent, though it does not explicitly name sibling tools.

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?

Usage context is implied: use this tool to archive a board with the option to reopen it later. However, there is no explicit guidance on when to choose this over delete_board or reopen_board, and no when-not-to-use conditions.

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

Deploy Server