Trello MCP Server

trello_search

Search Trello boards, cards, members, and organizations using a query with optional filters for model types and result limits.

Instructions

Search Trello for boards, cards, etc.

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": {
      "query": "<query>"
    },
    "name": "trello_search"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	The search query
`modelTypes`	No	Comma-separated list of model types (boards,cards,members,organizations)
`cards_limit`	No	Maximum number of cards to return
`boards_limit`	No	Maximum number of boards to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Description only says 'Search Trello' without detailing behavior: no mention of result scope, limits from parameters, pagination, authentication requirements, or side effects. With no annotations, the description carries full burden but provides very little transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words. However, it could be more informative without sacrificing conciseness. Loses a point for being overly terse.

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?

Missing essential context: no output schema, no description of return format or pagination. For a search tool with four parameters and no output schema, the description is incomplete and leaves the agent guessing about results.

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 each parameter has a description. The tool description adds no additional meaning beyond the schema; it merely states the search action. Baseline 3 is appropriate.

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 tool searches Trello for boards, cards, etc., which distinguishes it from sibling tools that perform specific CRUD operations on individual entities. The purpose is specific and immediately understandable.

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?

No guidance on when to use this tool versus alternatives like get_board or get_board_cards. Does not specify when to use search over direct retrieval.

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