zube-mcp

Overview Schema Source Related Servers Discussions Admin

list_project_cards

Retrieve project cards filtered by state, assignee, labels, number, or search, with customizable ordering and pagination.

Instructions

List cards scoped to a specific project with filtering and ordering.

number: filter by visible card number (e.g. 15293). assignee_ids: filter to cards assigned to these person IDs. label_names: filter to cards with these label names.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_project_cards"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`state`	No
`number`	No
`order_by`	No
`per_page`	No
`project_id`	Yes
`search_key`	No
`label_names`	No
`assignee_ids`	No
`workspace_id`	No
`category_name`	No
`order_direction`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 3, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'filtering and ordering' but only gives details for three filter parameters, leaving pagination, default ordering, state filtering, and other behaviors unexplained. It does not disclose rate limits, authentication needs, or the read-only nature explicitly, though 'List' implies read.

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 extremely concise and front-loaded with the primary purpose in the first sentence. The three parameter notes are each a single line, adding value without redundancy. Every sentence earns its place with clear, focused information.

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?

Despite the presence of an output schema, the description is incomplete for a tool with 12 parameters and no annotations. It fails to explain the majority of parameters, including pagination, ordering choices, state filtering, and search, leaving users to guess their semantics. The description covers only a fraction of the tool's capabilities.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameter meanings. It does explain three parameters (number, assignee_ids, label_names) with concrete examples, but nine other parameters remain entirely unexplained, including page, per_page, state, order_by, order_direction, search_key, category_name, and workspace_id. This partial coverage is insufficient for a tool with 12 parameters.

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 the tool's function with a specific verb ('List') and resource ('cards'), and scopes it to 'a specific project', distinguishing it from sibling tools like list_cards, list_epic_cards, and list_triage_cards. The inclusion of 'filtering and ordering' further defines its purpose.

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 clearly implies use for listing cards within a specific project, providing context for when it should be used over the broader list_cards tool. However, it does not explicitly mention alternatives or state when not to use it, so it stops short of full usage guidance.

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