Skip to main content
Glama
kanbanzone

Kanban Zone MCP Server

Official
by kanbanzone

Search cards by title or number

kanbanzone_search_cards
Read-onlyIdempotent

Search across all cards in your organization by title or card number. Optionally filter by board, include archived cards, and set page size.

Instructions

Full-text search across cards in your organization. Matches card titles and card numbers. Task, comment, and attachment text are not searched in this version. Results are sorted by relevance (best match first).

Mirror cards: results are returned per (card, board) pair — a card mirrored to two boards that matches the query appears twice, each with that board's bucket, label, owner, and watchers. Use the returned board field to know which board to act on.

Args:

  • q (string, required): search text, minimum 2 characters.

  • board (string, optional): board publicId to narrow the search to one board. Omit to search across every board in the org.

  • include_archived (boolean, optional): include archived cards.

  • page (number, optional, default 1).

  • count (number, optional, default 20, max 100).

  • response_format ("markdown" | "json").

Examples:

  • "Search for cards mentioning billing"

  • "Find cards about webhook on the OeMrbG8g board"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch text (min 2 characters).
boardNo
include_archivedNo
pageNo1-based page number.
countNoItems per page (1-100, default 20).
response_formatNoOutput format. 'markdown' (default) is human-readable; 'json' is the raw structured payload.markdown
Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the tool is safe to use. The description adds useful behavioral details such as relevance sorting, mirror card per-board results, and scope of search. No contradictions with annotations.

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 well-structured with a clear summary paragraph, a specific note on mirror cards, a parameter list, and examples. Every sentence adds value without redundancy, and the most important information is front-loaded.

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?

Given no output schema, the description explains return behavior (relevance sorting, mirror cards appearing twice, board field). It covers all parameters and usage notes comprehensively. Minor omission: does not explicitly state the default response format's human-readable structure.

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

Parameters5/5

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

Schema description coverage is 67%, but the description compensates by providing detailed explanations for all parameters, including board and include_archived which lacked schema descriptions. It also specifies defaults, constraints (min 2 chars, max 100 count), and the response_format enum meaning.

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?

The description clearly states 'Full-text search across cards' and specifies that it matches card titles and numbers, not task/comment/attachment text. This clearly differentiates it from siblings like kanbanzone_get_card (by ID) and kanbanzone_list_cards (list all).

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

Usage Guidelines4/5

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

The description provides context on when to use the tool (full-text search) and includes limitations (what is not searched). It also explains mirror card behavior and provides examples, but it does not explicitly state when not to use it or compare to alternatives like list_cards or get_card.

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/kanbanzone/kanban-zone-mcp-server'

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