Skip to main content
Glama
Sign In

Help by DeltaBreen

by eu.deltabreen
OverviewDiscussionsAdmin

list_tickets

Read-only

The workspace's tickets, most recently changed first (or most urgent first), 30 a page. Each has an id (use it with the other ticket tools), a number, a subject, who it is from, its status, its priority and its tags.

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
tagNoOnly tickets carrying this tag.
modeNo"live" (the default) or "test". Test tickets come from a site's test key.
sortNo"recent" (the default: most recently changed first) or "priority" (most urgent first).
teamNoOnly one team's tickets, by the team's name; "mine" for the teams of the person you act for, "none" for tickets no team has.
viewNoWhich tickets: "open" (waiting on the team, the default), "on_hold" (waiting on someone else), "pending" (waiting on the customer), "closed", "all", "spam", or "due" (open tickets with a time to reply by, soonest first, so late ones come first; each has `reply_due_at`).
fieldNoOnly tickets whose form was answered a certain way: a field's key, a colon and the value, like "category:billing". Keys and values are in get_form_fields.
beforeNoFor the next page: the `next` value the last call returned.
searchNoWords to look for in a ticket's subject and in every message on it (each word may be the start of a word; all must be there), or a ticket number like "#12". A ticket found by a message has `matched`: the start of that message.
priorityNoOnly tickets of this priority: "low", "normal", "high" or "urgent".
product_idNoOnly tickets of this site (an id from list_products).
assigned_toNo"me" for tickets assigned to the person you act for, "none" for unassigned, or a teammate's id from list_teammates.
customer_idNoOnly tickets from one customer: the `requester.id` of one of their tickets (from get_ticket). Lists every ticket of theirs, in the mode they wrote in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / assigned_to / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / before / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / customer_id / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / field / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / mode / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / priority / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / product_id / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / search / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / sort / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / tag / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / team / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedInput schema / properties / view / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already declared, the description adds useful behavioral context: default sorting behavior, an alternative priority sort, page size of 30, and the fields each ticket includes. It does not mention permission requirements or filtering behavior, but for a read-only listing tool the added disclosure is solid.

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 two dense sentences with no wasted text. The core listing behavior and pagination are front-loaded, followed by the ticket shape and the practical note about using the id with other tools.

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?

For a tool with 12 optional parameters, rich schema descriptions, no output schema, and read-only annotations, the description gives enough context to select and call it correctly. It covers scope, ordering, page size, returned fields, and id usage; the omitted filter details are fully handled by the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 12 parameters in detail. The description adds the page size and summarizes sort behavior, but it does not meaningfully elaborate on the many filters beyond what the schema provides.

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 description clearly identifies the resource and scope: 'The workspace's tickets' with sorting, pagination, and returned fields. It implicitly distinguishes the plural listing operation from the singular get_ticket by saying the returned id should be used with other ticket tools, but it does not explicitly name alternatives.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use list_tickets instead of get_ticket, ticket_counts, or other ticket tools. The phrase 'use it with the other ticket tools' only explains what to do with the returned id, not when this listing tool is the right choice.

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

All Help by DeltaBreen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources