Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_tickets

Read-onlyIdempotent

List paginated tickets with optional field selection, structured filters, and cursor-based pagination. Default returns thin projection; use verbose for full details.

Instructions

Returns tickets as paginated skeletons (id, title, active, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true for full bodies. Scope-gated, requires the instance to be configured at scope config_plus_audits or full; on config you get a scope_blocked envelope. For specific lookups prefer search (full Zendesk query syntax: type:ticket status:open), list_tickets over a busy instance pulls everything and is rarely what you want. For a single ticket's context use get_ticket with include_comments / include_audits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return. Default 100. The full corpus is fetched and cached server-side; this only limits what the response carries.
cursorNoOpaque pagination token from a previous response. Slices the next page from the cached corpus. Stale cursors (older than the cache TTL) auto-reset to offset 0 and set cursor_invalidated: true.
fieldsNoWhitelist of field names. Overrides the default projection. Use to opt into extra fields (e.g. ["id","title","active","position","category_id","updated_at"]) without going fully verbose.
filterNoStructured filter applied to the cached corpus before slicing. Supported keys: active (bool), category_id (number/string), title_contains (string, case-insensitive), updated_since (ISO timestamp). Unsupported keys are ignored with a note in the response.
refreshNoBypass cache and re-fetch from Zendesk
verboseNoReturn full ticket objects instead of the thin projection
instanceNoOverride the sticky instance for this call
Behavior5/5

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

Discloses scope-gating, caching behavior, pagination via cursor with stale cursor handling, filter key restrictions, and refresh option. Adds significant context beyond annotations.

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?

Front-loaded with main output, then parameter options, scope warning, and usage advice. Dense yet clear; every sentence adds value without fluff.

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?

No output schema, but description covers return formats (skeletons vs full), all parameters, caching, pagination, filtering, and alternatives. Comprehensive for a list tool.

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

Parameters5/5

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

Schema coverage is 100%. Description adds meaning to each parameter: explains default limit, cursor behavior, supported filter keys, refresh bypass, and verbose full bodies. Goes beyond schema descriptions.

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 it returns tickets as paginated skeletons with specific fields. Distinguishes from siblings like search and get_ticket with explicit usage guidance.

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 advises when to use alternatives: 'For specific lookups prefer search' and 'For a single ticket's context use get_ticket'. Also explains scope restrictions.

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

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/rlowndes9/zendesk-mcp-server'

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