Skip to main content
Glama

fizzy_search

Search cards using filters for tags, assignees, boards, and categories. Returns paginated results sorted by criteria.

Instructions

Search for cards with filters. Find cards matching criteria or review board contents.

When to use:

  • Find cards by tag, assignee, or board

  • Filter by index category (closed, stalled, golden, etc.)

Don't use when: You already know the card number — use fizzy_get_card instead.

Arguments:

  • account_slug (optional): Uses session default if omitted

  • board_id (optional): Filter to cards on this board

  • indexed_by (optional): Filter by index category: closed | not_now | all | stalled | postponing_soon | golden

  • tag_ids (optional): Filter to cards with ALL these tag IDs

  • assignee_ids (optional): Filter to cards assigned to ANY of these user IDs

  • sorted_by (optional): Sort order: newest | oldest | recently_active

  • terms (optional): Search terms to filter cards by text content

  • limit (optional): Max items, 1-100 (default: 25)

  • cursor (optional): Continuation cursor from previous response

Returns: JSON with items and pagination metadata.

{"items": [{"number": 42, "title": "...", ...}], "pagination": {"returned": 25, "has_more": true, "next_cursor": "..."}}

Related: Use card number with fizzy_get_card for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_slugNoAccount slug (e.g., 'acme-corp'). Uses session default if omitted.
board_idNoFilter to cards on this board ID.
indexed_byNoFilter by index category: closed | not_now | all | stalled | postponing_soon | golden.
tag_idsNoFilter to cards with ALL these tag IDs.
assignee_idsNoFilter to cards assigned to ANY of these user IDs.
sorted_byNoSort order: newest | oldest | recently_active.
termsNoSearch terms to filter cards by text content.
creator_idsNoFilter to cards created by these user IDs.
closer_idsNoFilter to cards closed by these user IDs.
card_idsNoFilter to specific card IDs.
assignment_statusNoFilter by assignment status: unassigned.
creationNoFilter by creation date range: today | yesterday | thisweek | thismonth | last7 | last14 | last30.
closureNoFilter by closure date range: today | yesterday | thisweek | thismonth | last7 | last14 | last30.
limitYesMax items to return (1-100, default: 25).
cursorNoContinuation cursor from previous response. Omit to start fresh.
Behavior3/5

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

No annotations provided; description covers functionality and return format, but doesn't explicitly state read-only nature or any side effects. Adequate but not fully transparent.

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?

Well-structured with sections, front-loaded main purpose, efficient bullet points for arguments, no unnecessary text.

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?

With 15 parameters, no output schema, and no annotations, description covers all parameters, return format, pagination, and related tools. Could mention error handling but sufficient for usage.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value with structured argument list, defaults, and pagination details, providing moderate extra context.

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?

Clearly states it searches for cards with filters, lists specific use cases (tag, assignee, board, index category), and distinguishes from sibling tool fizzy_get_card for when card number is known.

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?

Explicit 'When to use' and 'Don't use when' sections, with clear guidance on alternatives (fizzy_get_card). Provides context for filter usage.

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/davegomez/fizzy-mcp'

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