zendesk-mcp

Overview Schema Source Related Servers Discussions Admin

zendesk_get_tickets

List Zendesk tickets with pagination and sorting. Specify page, per-page count, sort-by field, and sort order to retrieve the desired ticket page.

Instructions

List Zendesk tickets with pagination. page: 1-based page number. per_page: max 100. sort_by: created_at, updated_at, priority, or status. sort_order: asc or desc. Returns tickets plus pagination metadata.

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": "zendesk_get_tickets"
  }
}

Input Schema

Name	Required	Default
`page`	No
`sort_by`	No	created_at
`per_page`	No
`sort_order`	No	desc

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1May 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Discloses pagination behavior (page basis, per_page max, sort options) and that the response includes pagination metadata. No annotations present, so description carries full burden; it sufficiently covers functional behavior.

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 sentences with no redundancy. Purpose and parameter details are front-loaded. Every 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?

Given the tool's simplicity (no required params, no enums) and the presence of an output schema (not shown), the description adequately covers usage and return format. For a list tool, this is complete.

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?

With 0% schema coverage, the description fully explains all 4 parameters: page (1-based), per_page (max 100), sort_by (four valid values), sort_order (asc/desc). This adds essential meaning beyond the 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 'List Zendesk tickets with pagination' – a specific verb and resource. Distinguishes from siblings like zendesk_get_ticket (single ticket) and zendesk_search_tickets (search-based).

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?

Describes pagination and parameters, implying usage for listing all tickets with sorting and filtering. However, lacks explicit guidance on when to use this vs alternatives like search_tickets or get_ticket.

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