Skip to main content
Glama

zendesk_set_ticket_status

Set the status of a Zendesk ticket to new, open, pending, hold, solved, or closed.

Instructions

Set the status of a Zendesk ticket. Valid statuses: new, open, pending, hold, solved, closed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYes
statusYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler function that validates status, creates a Zendesk Ticket object, sets its status, and updates it via the API. Handles config errors, 'not found' errors, and other API errors.
    def _set_ticket_status_data(ticket_id: int, status: str) -> str:
        if status not in _VALID_STATUSES:
            return f"Invalid status '{status}'. Valid values: {', '.join(sorted(_VALID_STATUSES))}"
        try:
            client = get_client()
            ticket = Ticket(id=ticket_id)
            ticket.status = status
            client.tickets.update(ticket)
            return f"Ticket #{ticket_id} status set to '{status}'."
  • Set of valid statuses used for input validation of the status parameter.
    _VALID_STATUSES = {"new", "open", "pending", "hold", "solved", "closed"}
  • The MCP tool registration via @mcp.tool() decorator, defining the tool name 'zendesk_set_ticket_status' with typed parameters ticket_id (int) and status (str), and delegating to the handler.
    @mcp.tool()
    def zendesk_set_ticket_status(ticket_id: int, status: str) -> str:
        """Set the status of a Zendesk ticket. Valid statuses: new, open, pending, hold, solved, closed."""
        return _set_ticket_status_data(ticket_id, status)
  • Server-level import and call of the registration function that wires the tool into the MCP server.
    from zendesk_mcp.tools.update_ticket import register_update_ticket_tools
    from zendesk_mcp.tools.time_tracking import register_time_tracking_tools
    from zendesk_mcp.tools.git_zen import register_git_zen_tools
    
    register_ticket_tools(mcp)
    register_comments_tools(mcp)
    register_attachment_tools(mcp)
    register_gitlab_context_tools(mcp)
    register_write_comment_tools(mcp)
    register_update_ticket_tools(mcp)
    register_time_tracking_tools(mcp)
    register_git_zen_tools(mcp)
Behavior2/5

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

No annotations provided, and the description does not disclose side effects (e.g., notifications, field changes), permissions required, or reversibility. Only states the mutation operation without behavioral context.

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 efficient sentences with no fluff. The first sentence states purpose and resource, the second provides valid values. Front-loaded and every word earns its place.

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

Completeness3/5

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

For a 2-parameter mutation tool with an output schema (exists but not shown), the description is minimally adequate. However, lacks context on status transitions, error conditions, or required permissions that would make it more complete given no annotations.

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?

Although schema coverage is 0%, the description lists the valid status values, adding crucial meaning to the status parameter beyond the raw schema. No extra detail for ticket_id, but the value lies in enumerating allowed statuses.

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 'Set the status of a Zendesk ticket' with a specific verb (Set) and resource (status). Lists valid statuses, distinguishing it from sibling tools like 'zendesk_assign_ticket' or 'zendesk_post_comment'.

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?

Provides valid statuses but no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of status transition rules or restrictions (e.g., cannot set closed to open).

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

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