Skip to main content
Glama

get_ticket

Retrieve a specific Zendesk support ticket using its unique ID to access ticket details and manage support workflows.

Instructions

Retrieve a Zendesk ticket by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYesThe ID of the ticket to retrieve

Implementation Reference

  • The actual implementation of the get_ticket functionality in the Zendesk client.
    def get_ticket(self, ticket_id: int) -> Dict[str, Any]:
        """
        Query a ticket by its ID
        """
        try:
            ticket = self.client.tickets(id=ticket_id)
            return {
                'id': ticket.id,
                'subject': ticket.subject,
                'description': ticket.description,
                'status': ticket.status,
                'priority': ticket.priority,
                'created_at': str(ticket.created_at),
                'updated_at': str(ticket.updated_at),
                'requester_id': ticket.requester_id,
                'assignee_id': ticket.assignee_id,
  • Tool definition for get_ticket in the MCP server.
        name="get_ticket",
        description="Retrieve a Zendesk ticket by its ID",
        inputSchema={
            "type": "object",
            "properties": {
                "ticket_id": {
                    "type": "integer",
                    "description": "The ID of the ticket to retrieve"
                }
            },
            "required": ["ticket_id"]
        }
    ),
  • The tool execution handler for get_ticket, which calls the zendesk_client method.
    if name == "get_ticket":
        if not arguments:
            raise ValueError("Missing arguments")
        ticket = zendesk_client.get_ticket(arguments["ticket_id"])
        return [types.TextContent(
            type="text",
            text=json.dumps(ticket)
        )]
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves a ticket, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or what happens if the ticket ID is invalid. This leaves significant gaps for an agent to understand how to use it effectively.

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, clear sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary details.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., ticket details, error responses) or address potential complexities like authentication or rate limits. For a tool with no structured support, more context is needed to guide an agent fully.

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 100%, so the input schema already documents the 'ticket_id' parameter as an integer. The description adds minimal value by mentioning 'by its ID', which aligns with the schema but doesn't provide additional context like format examples or constraints beyond what's in the structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieve') and resource ('a Zendesk ticket by its ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_tickets' (plural) or 'search_tickets' which suggests it's for single-ticket lookup versus batch operations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_tickets' or 'search_tickets'. The description implies it's for retrieving a specific ticket by ID, but it doesn't explicitly state this as the primary use case or mention prerequisites such as needing a valid ticket ID.

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

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