Skip to main content
Glama
SShadowS

Zendesk MCP Server

by SShadowS
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

search

Search Zendesk tickets, users, organizations, groups, and articles using query operators to filter by status, assignee, dates, tags, and more.

Instructions

Search Zendesk tickets, users, organizations, groups, and Help Center articles using Zendesk's full search query language. The query parameter supports operators (combined with spaces, implicit AND): type:ticket|user|organization|group|article, recipient:<email>, assignee:<email|me|none>, requester:<email>, submitter:<email>, status<solved (also >, <=, >=), tags:<tag>, brand:<id>, group:<id>, created>2026-05-01 (also updated, solved_at, due_at), priority:high|normal|low|urgent, via:web|email|chat|phone, plus full-text on subject/description. Combine for precision (e.g. type:ticket recipient:support@acme.com status<solved created>2026-05-01). IMPORTANT: default sort is relevance, not date — for chronological results pass sort_by:created_at (or updated_at) with sort_order:desc. Use this instead of list_tickets whenever you need filtering by recipient/assignee/tag/status/dates or full-text search; list_tickets has no filter parameters. Reference: https://support.zendesk.com/hc/en-us/articles/4408886879258

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesZendesk search query. Use operators like `type:ticket`, `recipient:<email>`, `assignee:<email|me>`, `tags:<tag>`, `status<solved`, `created>YYYY-MM-DD`. Combine with spaces (implicit AND). Example: `type:ticket recipient:support@acme.com status<solved`.
sort_byNoSort field — `created_at`, `updated_at`, `priority`, `status`, `ticket_type`. Defaults to relevance (NOT date) when omitted; pass `created_at` for chronological results.
sort_orderNo`desc` for newest-first (typical), `asc` for oldest-first. Only takes effect when `sort_by` is set.
pageNo1-based page number. Defaults to 1.
per_pageNoResults per page, 1-100. Defaults to 100. Combined with `page` to walk large result sets — `count` in the response tells you the total.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses default sort (relevance), need to specify sort_by for chronological ordering, and details operators. Minor gap: no mention of rate limits or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is long but well-structured: starts with purpose, then operator details, then critical sort behavior, then when-to-use. Every sentence adds value; however, could be slightly more concise.

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 5 parameters, no output schema, and complexity of search syntax, the description covers query operators, sorting, pagination, and usage guidance comprehensively. Leaves no major gaps for effective tool invocation.

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 coverage is 100%, but description adds significant value beyond schema: explains query operators with examples, sorting defaults, and pagination hints. Baseline 3, plus extra context.

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?

The description clearly states it searches multiple Zendesk entities using a query language. It explicitly differentiates from list_tickets by noting the filtering capabilities that list_tickets lacks.

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?

Provides explicit guidance on when to use this tool vs list_tickets (use when filtering by recipient/assignee/tag/status/dates or full-text search). Also includes a reference link for more details.

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

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