Skip to main content
Glama

list_tickets

List a project's tickets (rows of its Tickets datastore), open work first, newest first. Done tickets are hidden unless include_done=true or status includes "Done".

Descriptions are cut to a 300-character preview unless full_descriptions=true. Each ticket has a ticket_id for update_ticket.

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": {
      "page_id": "<page_id>"
    },
    "name": "list_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax tickets to return (default 100, max 500)
statusNoOnly these statuses (optional)
page_idYesAny page in the project: its Tickets page, the project root page, or any page under it. Find the root with find_page_by_root_path(root_path=<repo path>) if you have no page id.
include_doneNoInclude Done tickets (default false)
full_descriptionsNoReturn full descriptions (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses meaningful behavior: default sort order, default exclusion of Done items, and that ticket descriptions are truncated to a 300-character preview unless full_descriptions=true. It stops short of describing permissions, error conditions, or pagination beyond the limit parameter.

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?

Roughly three short sentences, front-loaded with the core listing behavior, followed by the filtering rule and the truncation caveat. The sentence starting "Descriptions are cut..." is slightly ambiguous about whether it means ticket descriptions, but nothing is wasted.

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?

There is no output schema, so the description must speak for return values, and it does: ticket rows, a ticket_id usable with update_ticket, and truncated description text. For a 5-parameter read tool this is nearly complete, though it does not enumerate the remaining ticket fields an agent will see.

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 the baseline is 3, but the description adds real value by explaining the interaction between include_done and status (either one surfaces Done tickets) — a relationship the per-parameter schema text does not convey. It also explains what full_descriptions actually toggles, namely the 300-character preview cutoff.

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 opens with a specific verb and resource: "List a project's tickets (rows of its Tickets datastore)", which pins down both the operation and the underlying object model. It also clarifies ordering (open work first, newest first), so an agent knows exactly what this returns versus a generic page-listing tool.

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?

It gives clear conditional guidance for the non-obvious filtering case: Done tickets are hidden unless include_done=true or status includes "Done". It does not name an alternative tool for listing pages or blocks, so the when-not-to-use routing is left implicit, but the in-tool usage conditions are explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources