Trello MCP Server

set_active_board

Define which Trello board to use for all subsequent operations by providing its board ID.

Instructions

Set the active board for future operations

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

Input Schema

Name	Required	Description	Default
`boardId`	Yes	ID of the board to set as active

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It indicates a state mutation ('set') but does not disclose side effects such as whether the change is persistent, what happens to the previous active board, or any authentication requirements. This is insufficient for an agent to understand the behavior fully.

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 a single concise sentence that front-loads the core action. It contains no unnecessary words and is easy to parse. Every part earns its place.

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 simple tool with one parameter and no output schema, the description is adequate but minimal. It does not explain the importance of setting the active board for subsequent operations, nor does it clarify the tool's role in a workflow. More context would be beneficial.

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?

The parameter 'boardId' is fully described in the input schema with a clear description. The tool description adds no additional meaning beyond the schema, so it meets the baseline for a schema with 100% coverage.

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 tool's verb ('Set') and resource ('active board'), indicating its primary function. It distinguishes itself from siblings like 'get_active_board_info' and 'list_boards' by being the only tool that sets the active board. However, it could be more explicit about the meaning of 'active board' in the broader context.

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?

The description implies use before operations that depend on an active board but does not provide explicit guidance on when to use it, when not to use it, or mention any prerequisites or alternatives. No context is given about required prior actions or the effect on subsequent tool calls.

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