Skip to main content
Glama

search

Read-only

Find Trello cards and boards by query, with optional board, type, and pagination filters.

Instructions

Search Trello for cards and boards.

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

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
pageNoCard results page (0-based)
limitNoMax cards per page
queryYes
boardIdNoRestrict the search to one board
modelTypesNoComma-separated: cards,boards,organizations,memberscards,boards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds nothing about search scope, whether queries match board names, card titles, or descriptions, how results are ordered, or that non-card model types can be returned.

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?

A single front-loaded sentence with no wasted words. It is terse to the point of under-specification, but nothing in it is redundant or padded.

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?

With six parameters, pagination, and an open-world result set, a one-clause description leaves too much unspecified: no mention of pagination behavior, no hint that modelTypes broadens results beyond cards and boards, and no output shape (there is no output schema to compensate).

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 83%, so the schema itself documents lang, page, limit, boardId, and modelTypes. The description adds no meaning beyond that, but the high coverage justifies the baseline 3.

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 names a specific verb (search) and resource (Trello cards and boards), so the basic purpose is unmistakable. It does not differentiate from siblings such as get_cards or list_boards, and it omits organizations and members even though modelTypes supports them.

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?

There is no guidance on when to use this tool versus the many list/get siblings. An agent must infer that this is the free-text query tool rather than a filtered enumeration from the name and schema alone.

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