Skip to main content
Glama
VeryLongOrgNameSuchWow

kanbantool-mcp

by VeryLongOrgNameSuchWow
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_tasks

Read-only

Search tasks across boards using a query DSL with filters for assignee, name, priority, tags, due date, and more. Scope to one board or all, with pagination.

Instructions

Search tasks across boards using Kanban Tool's query DSL.

query is forwarded verbatim — do not URL-encode, do not wrap the whole expression in quotes. Quote individual values only when they contain spaces (e.g. name:"ship the thing"). Terms combine with spaces and are AND-ed.

Supported operators:

  • @username — assignee, e.g. @alice

  • name:<text> — title contains

  • priority:<level> — e.g. priority:high

  • tags:<tag> — tag match

  • due_date=<iso-date> — e.g. due_date=2026-05-01

  • subtasks_count<N> — also >, =

  • archived:<bool> — include archived

Unknown operators silently return zero results, so don't invent syntax for things the DSL doesn't cover (comment full-text, fuzzy match) — say so instead. board_id scopes to one board (omit to search all visible). limit is clamped to 50; paginate further with page (1-indexed).

Returns a SearchResults wrapper:

  • results — the list of matched Task objects on this page.

  • total_count — total matches across all pages (from the API's pagination envelope; None if the API omits the envelope).

  • page — 1-indexed page number of this response.

  • has_more — True when at least one further page exists. Use this to decide whether to bump page and call again, instead of heuristics on len(results) == limit (which is wrong on the last page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
board_idNo
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Discloses that query is forwarded verbatim, unknown operators return zero results, limit clamped to 50, page is 1-indexed, and details the return structure (has_more, total_count, page). Adds value beyond the readOnlyHint annotation.

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?

Well-structured with sections and bullet points, front-loaded with purpose. Slightly long but justified by the complexity of the query DSL and pagination. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters and an output schema (SearchResults), the description covers all aspects: query DSL details, pagination behavior, and return fields (results, total_count, page, has_more). No gaps.

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 has no parameter descriptions (0% coverage). The description compensates fully: explains query DSL, board_id optionality, limit clamping, page indexing. Provides operator syntax and constraints.

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 it searches tasks across boards using Kanban Tool's query DSL, distinguishing it from siblings like get_task (single task) and list_boards.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use, query syntax (verbatim, no URL-encode), quoting rules, operators, board_id scoping, limit clamping, pagination, and warns about unknown operators returning zero results. Differentiates from siblings.

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/VeryLongOrgNameSuchWow/kanbantool-mcp'

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