Skip to main content
Glama

list_tickets

Lists a project's tickets in plan order with status, dependencies, and blockers to identify ready work and determine the next ticket to handle.

Instructions

The project's tickets in plan order: id, label (the Linear identifier such as ENG-12, the GitHub identifier such as GH-12, else T), title, status (todo, in_progress, done, canceled), milestone, depends_on, the GitHub repo it changes (repo, owner/name, for a project that spans several), whether it is ready (all it depends on is done) or which tickets block it, the link when it lives in Linear or GitHub, and the id and title of each one's working doc, and who it is for (assignee, {id, name}, or null with assignee_raw as the source named them, and assignee_note: "assignee: Kiran" or "unowned (kiran@x.com is not on this cell)"). Work the ready tickets in this order. Also says where they live: linear is the Linear project and github the repo and issue label, each with when it was last synced (null when the project does not use it); with both null the tickets live in Tares. Read one with get_ticket to get its working doc.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful semantics: readiness means all dependencies are done, blocking relationships are returned, assignee resolution falls back to assignee_raw plus an assignee_note explaining why ownership failed, and null sync timestamps mean the source is unused. However, it says nothing about permissions, pagination, result size limits, or behavior when the project is empty, and most of its length is spent restating return fields that the output schema already defines.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one sprawling sentence that enumerates nearly every output field (id, label, title, status, milestone, depends_on, repo, link, working doc, assignee) even though an output schema exists, so a large share of the text does not earn its place. The genuinely useful rules — readiness, assignee fallback, null source meaning 'lives in Tares' — are buried mid-stream rather than front-loaded.

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

Completeness3/5

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

With a single optional parameter and an existing output schema, the tool is simple enough that the main missing piece is what `project` accepts and what the default resolves to. The description compensates by explaining source-of-truth resolution and assignee fallback semantics, but it never addresses the parameter, so an agent cannot confidently scope the call.

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% for the single `project` parameter, and the description never explains it — whether it takes a project name, id, or path, or what the empty default means (presumably the current project). The phrase 'The project's tickets' hints that scoping is by project but leaves format and default behavior entirely to inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening phrase 'The project's tickets in plan order' identifies the resource and the ordering, and the closing sentence routes detail-reading to get_ticket, so it is distinguishable from its sibling. The verb is only implied ('tickets in plan order') rather than stated as 'list', and the purpose statement is buried under a long field enumeration.

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 real operational guidance: 'Work the ready tickets in this order' tells the agent how to sequence its work, and 'Read one with get_ticket to get its working doc' names the alternative for per-ticket detail. There is no explicit when-not guidance (e.g., when to use list_tickets vs. list_milestones or get_ticket alone), which keeps it short of a 5.

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