Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr

Get Zendesk Ticket

get_ticket
Read-onlyIdempotent

Retrieve a Zendesk ticket by ID, including its live SLA state and optional comment thread. Returns ticket details like subject, status, assignee, and more.

Instructions

Retrieve a Zendesk ticket by ID, including its live SLA state (per-metric stage and breach countdown) when an SLA policy applies, plus its comments if requested. Returns ticket details (subject, status, priority, assignee, tags, description) and optionally all comments/internal notes. The per-ticket Show endpoint exposes no SLA, so the SLA block is resolved via a scoped search and may be absent for a very high-volume requester or a just-updated ticket; SLA targets and policy conditions live in list_sla_policies. This returns the ticket as it stands now; for the history of changes behind that state (who changed what, and when), use get_ticket_history. The comment thread is appended in one block — the first page of comments Zendesk returns, cut past the response character limit — so on a long ticket read it with list_ticket_comments, which pages the comments and returns the newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYesTicket ID — the numeric id of the ticket to fetch. Obtain it from search_tickets or list_tickets.
include_commentsNoWhen true, appends the full public comment and internal note thread to the response. Defaults to false to keep the payload small; enable it when you need the conversation, not just the ticket fields. On a long thread prefer list_ticket_comments — this flag appends one unpaginated block, so comments past Zendesk's first page are absent and the rest is cut at the response character limit.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses that SLA may be absent for very high-volume requesters or just-updated tickets, and that comments are cut at the response character limit if present. It also clarifies that the SLA block is resolved via a scoped search, not directly from the ticket endpoint. These details go beyond the readOnlyHint and openWorldHint annotations, making the tool's limitations transparent.

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 well-structured and front-loaded: the first sentence states the core action, then it details SLA behavior, comment inclusion, and alternatives. While lengthy, each clause serves a purpose (clarifying edge cases, redirecting to siblings) and there is no superfluous content. The logical flow from core function to caveats to related tools is clear.

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?

The description provides complete context for correct usage: it explains what the tool returns, when SLA may be missing, how comment inclusion works and its truncation risk, and directs users to the appropriate sibling tools for history (get_ticket_history) and paginated comments (list_ticket_comments). It also notes the source of ticket IDs (search_tickets or list_tickets), giving the agent everything needed to decide when and how to invoke this tool.

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?

The input schema already provides thorough descriptions for both ticket_id and include_comments, including how to obtain the ID and the pagination caveat for comments. The tool description adds no new parameter-specific information beyond what is already in the schema, so it does not meaningfully enhance parameter semantics.

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 the tool retrieves a Zendesk ticket by ID and explicitly lists the returned fields (subject, status, priority, assignee, tags, description) plus optional comments and SLA state. It distinguishes itself from siblings by noting that SLA is resolved via a scoped search (list_sla_policies) and that comments are unpaginated, steering users to list_ticket_comments for long threads and to get_ticket_history for change history.

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?

The description gives explicit when-to-use guidance: it explains that include_comments should be enabled only when the conversation is needed and defaults to false to keep the payload small. It further advises using list_ticket_comments for long threads because this tool appends a single unpaginated block that may be truncated, and get_ticket_history for historical changes. These alternatives are clearly named and conditions are stated.

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

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

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