Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Zendesk Tickets

list_tickets
Read-onlyIdempotent

List Zendesk tickets in ascending ID order using cursor-based pagination. Control page size with page_size and pass the returned cursor to get additional pages.

Instructions

List tickets with cursor-based pagination, in Zendesk's default order (ascending ticket id), not by recency. Page size is controlled by page_size (not per_page, which is the offset-based parameter used by search_tickets); paginate by passing the returned cursor. To find tickets by recency or any other criterion, use search_tickets with a query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response; omit for the first page.
page_sizeNoTickets per page (1-100, default 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"Pagination cursor from a previous response; omit for the first page."
    • addedInput schema / properties / page_size / description
      Added value: +"Tickets per page (1-100, default 100)."
  2. First observedv1.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Adds value beyond annotations by detailing cursor-based pagination, page_size naming convention vs per_page in search_tickets, and ordering behavior (ascending id, not recency).

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?

Two concise sentences, front-loaded with main action, no unnecessary words. Each sentence adds value.

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

Completeness5/5

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

Complete explanation for a simple list tool with two parameters, covers pagination, ordering, and comparison with sibling. No missing context.

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 already describes parameters well (100% coverage); description adds useful context about cursor usage and distinguishes page_size from per_page. Adds meaning beyond schema.

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 verb 'List' and resource 'tickets', distinguishes default ordering (ascending id) and pagination method, differentiating it from search_tickets.

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?

Explicitly tells when to use this vs search_tickets: for ordering by recency or other criteria, use search_tickets. Also mentions default ordering and pagination specifics.

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

Deploy Server

Other Tools