Zendesk Live MCP

get_live_ticket_detail

Fetch a live Zendesk ticket's details, optionally including its comments.

Instructions

Fetch one live Zendesk ticket, optionally including comments.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticket_id": "<ticket_id>"
    },
    "name": "get_live_ticket_detail"
  }
}

Input Schema

Name	Required	Description	Default
`ticket_id`	Yes
`include_comments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It indicates a read-only fetch via 'Fetch', but does not disclose potential limitations, authentication requirements, error behavior, or any other side effects. This is a significant gap for a tool with no annotation support.

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 a single, front-loaded sentence with no redundant information. It earns its place by stating the core action and the optional comment inclusion without wasted words.

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

Completeness2/5

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

No output schema exists, so the description should help the agent understand what the response contains. It only says 'ticket' without specifying fields or structure. It also lacks information on error handling and edge cases, making it incomplete for a tool with no annotations and no output schema.

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?

Schema description coverage is 0%, so the description must compensate. It does clarify that ticket_id identifies the specific ticket and that include_comments optionally includes comments, adding meaning beyond the bare parameter names. However, it does not explain types or defaults (already in schema) or any additional semantics, so it is only partially compensating.

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 specific action: fetch a single live Zendesk ticket, with an optional comments flag. The verb 'Fetch' and resource 'one live Zendesk ticket' are precise, and it distinguishes from sibling tools like search_live_tickets and report tools by focusing on a single ticket detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving one specific ticket, but it does not explicitly state when to use this tool versus alternatives like search_live_tickets. There is no mention of exclusions or alternative tools, so the guidance is only implied by the tool's purpose.

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

Deploy Server