Skip to main content
Glama
kanbanzone

Kanban Zone MCP Server

Official
by kanbanzone

List cards on a board

kanbanzone_list_cards
Read-onlyIdempotent

List cards on a Kanban board with filters for column, owner, label, or days since last update. Supports pagination and archived cards.

Instructions

List cards on a board with optional filters and pagination.

Args:

  • board (string, required): board publicId.

  • columns (string, optional): comma-separated column ObjectIds to restrict to.

  • owner (string, optional): account ObjectId or email — only cards owned by this person.

  • label (string, optional): label ObjectId or description string.

  • days_since_last_update (number, optional): only cards untouched for N+ days.

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

  • number (number, optional): fetch a single card by its #N number.

  • page (number, optional, default 1).

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

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

Examples:

  • "What cards are in progress on the OeMrbG8g board?"

  • "List my cards owned by alice@example.com"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardYes
columnsNo
ownerNo
labelNo
days_since_last_updateNo
include_archivedNo
numberNo
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 declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by specifying pagination behavior (page, count, default 20, max 100) and output format options (markdown or json), which are beyond what annotations provide. No contradiction.

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 concise with a clear structure: a one-line summary, an Args list, and Examples. Every sentence adds value, and the examples are practical. No unnecessary content.

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?

Given 10 parameters and no output schema, the description fully explains each parameter's meaning and usage. It includes pagination details, output format options, and illustrative examples, making the tool's behavior complete for an agent.

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?

With schema description coverage at 30%, the description compensates well. It provides meaningful explanations for all 10 parameters, e.g., 'board publicId', 'comma-separated column ObjectIds', 'account ObjectId or email', 'label ObjectId or description string', 'only cards untouched for N+ days'. This adds significant context beyond the schema.

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 'List cards on a board with optional filters and pagination.' This specific verb-resource pair distinguishes it from siblings like kanbanzone_get_card (single card) and kanbanzone_search_cards (search across boards).

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

Usage Guidelines3/5

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

The description provides examples that imply usage contexts, but does not explicitly state when to use this tool versus alternatives like search_cards. Usage guidelines are implied rather than direct.

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