Skip to main content
Glama

list_tickets

Retrieve and manage tickets in mcptix with filtering, sorting, and pagination options to streamline project task tracking and organization.

Instructions

List tickets with optional filtering, sorting, and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tickets to return
offsetNoNumber of tickets to skip
orderNoSort orderdesc
priorityNoFilter by priority
searchNoSearch term for title and description
sortNoSort fieldupdated
statusNoFilter by status

Implementation Reference

  • The handler function that implements the list_tickets tool logic. It processes input arguments to filter, sort, and paginate tickets using the TicketQueries database interface.
    export function handleListTickets(ticketQueries: TicketQueries, args: any): ToolResponse {
      Logger.debug('McpServer', `handleListTickets called with args: ${JSON.stringify(args)}`);
    
      const filters = {
        status: args.status,
        priority: args.priority,
        search: args.search,
      };
    
      Logger.debug('McpServer', `Using filters: ${JSON.stringify(filters)}`);
    
      const tickets = ticketQueries.getTickets(
        filters,
        args.sort || 'updated',
        args.order || 'desc',
        args.limit || 100,
        args.offset || 0,
      );
    
      return createSuccessResponse(tickets);
    }
  • The input schema definition for the list_tickets tool, specifying parameters for filtering by status/priority/search, sorting, and pagination.
      name: 'list_tickets',
      description: 'List tickets with optional filtering, sorting, and pagination',
      inputSchema: {
        type: 'object',
        properties: {
          status: {
            type: 'string',
            description: 'Filter by status',
            enum: ['backlog', 'up-next', 'in-progress', 'in-review', 'completed'],
          },
          priority: {
            type: 'string',
            description: 'Filter by priority',
            enum: ['low', 'medium', 'high'],
          },
          search: {
            type: 'string',
            description: 'Search term for title and description',
          },
          sort: {
            type: 'string',
            description: 'Sort field',
            default: 'updated',
          },
          order: {
            type: 'string',
            description: 'Sort order',
            enum: ['asc', 'desc'],
            default: 'desc',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of tickets to return',
            default: 100,
          },
          offset: {
            type: 'number',
            description: 'Number of tickets to skip',
            default: 0,
          },
        },
      },
    },
  • Registration of the list_tickets handler in the MCP tool call switch statement within the setupToolHandlers function.
    case 'list_tickets':
      return handleListTickets(ticketQueries, args);
    case 'get_ticket':
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'optional filtering, sorting, and pagination' but lacks critical behavioral details: it doesn't specify default behavior beyond what's in the schema (e.g., default sort order), doesn't mention rate limits, authentication needs, or what happens with invalid parameters. For a list operation with 7 parameters, this leaves significant gaps in understanding how the tool behaves in practice.

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 a single, efficient sentence that front-loads the core purpose ('List tickets') and succinctly lists key features. Every word earns its place with no redundancy or fluff, making it easy for an agent to parse quickly while covering essential aspects.

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?

Given the tool's moderate complexity (7 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action and features but lacks details on behavioral traits, output format, or error handling. Without annotations or output schema, the agent is left with incomplete context for reliable invocation, though the schema provides solid parameter documentation.

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 fully documents all 7 parameters. The description adds minimal value beyond the schema by summarizing the optional features (filtering, sorting, pagination), but doesn't provide additional context like parameter interactions or usage examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't detract either.

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 states the verb 'List' and resource 'tickets', making the purpose unambiguous. It distinguishes from siblings like 'get_ticket' (singular) and 'search_tickets' (implied broader search), though it doesn't explicitly differentiate from 'search_tickets' which might have overlapping functionality. The description is specific about the action but could be more precise about scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_tickets' or 'get_ticket'. The description mentions optional filtering, sorting, and pagination, but doesn't specify contexts or exclusions. Without explicit usage rules, the agent must infer based on tool names alone, which is insufficient for reliable selection.

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

Related 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/ownlytics/mcptix'

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