Skip to main content
Glama
koundinya

Zendesk MCP Server

by koundinya

zendesk_update_ticket

Modify Zendesk ticket properties such as priority, status, assignee, tags, subject, and type by specifying the ticket ID.

Instructions

Update a Zendesk ticket's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignee_idNoThe ID of the agent to assign the ticket to
priorityNoThe new priority of the ticket
statusNoThe new status of the ticket
subjectNoThe new subject of the ticket
tagsNoTags to set on the ticket (replaces existing tags)
ticket_idYesThe ID of the ticket to update
typeNoThe new type of the ticket

Implementation Reference

  • The handler function for zendesk_update_ticket that constructs the update data from inputs and calls the Zendesk tickets.update API.
    async ({ ticket_id, subject, status, priority, type, assignee_id, tags }) => {
      try {
        const ticketData: any = {
          ticket: {}
        };
    
        // Only add properties that are provided
        if (subject) ticketData.ticket.subject = subject;
        if (status) ticketData.ticket.status = status;
        if (priority) ticketData.ticket.priority = priority;
        if (type) ticketData.ticket.type = type;
        if (assignee_id) ticketData.ticket.assignee_id = parseInt(assignee_id, 10);
        if (tags) ticketData.ticket.tags = tags;
    
        const result = await new Promise((resolve, reject) => {
          (client as any).tickets.update(parseInt(ticket_id, 10), ticketData, (error: Error | undefined, req: any, result: any) => {
            if (error) {
              console.log(error);
              reject(error);
            } else {
              resolve(result);
            }
          });
        });
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Error: ${error.message || 'Unknown error occurred'}`
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters for updating a Zendesk ticket.
    {
      ticket_id: z.string().describe("The ID of the ticket to update"),
      subject: z.string().optional().describe("The new subject of the ticket"),
      status: z.enum(['new', 'open', 'pending', 'hold', 'solved', 'closed']).optional().describe("The new status of the ticket"),
      priority: z.enum(['low', 'normal', 'high', 'urgent']).optional().describe("The new priority of the ticket"),
      type: z.enum(['problem', 'incident', 'question', 'task']).optional().describe("The new type of the ticket"),
      assignee_id: z.string().optional().describe("The ID of the agent to assign the ticket to"),
      tags: z.array(z.string()).optional().describe("Tags to set on the ticket (replaces existing tags)")
    },
  • Full registration of the zendesk_update_ticket tool with MCP server using server.tool, including description, schema, and inline handler.
    server.tool(
      "zendesk_update_ticket",
      "Update a Zendesk ticket's properties",
      {
        ticket_id: z.string().describe("The ID of the ticket to update"),
        subject: z.string().optional().describe("The new subject of the ticket"),
        status: z.enum(['new', 'open', 'pending', 'hold', 'solved', 'closed']).optional().describe("The new status of the ticket"),
        priority: z.enum(['low', 'normal', 'high', 'urgent']).optional().describe("The new priority of the ticket"),
        type: z.enum(['problem', 'incident', 'question', 'task']).optional().describe("The new type of the ticket"),
        assignee_id: z.string().optional().describe("The ID of the agent to assign the ticket to"),
        tags: z.array(z.string()).optional().describe("Tags to set on the ticket (replaces existing tags)")
      },
      async ({ ticket_id, subject, status, priority, type, assignee_id, tags }) => {
        try {
          const ticketData: any = {
            ticket: {}
          };
    
          // Only add properties that are provided
          if (subject) ticketData.ticket.subject = subject;
          if (status) ticketData.ticket.status = status;
          if (priority) ticketData.ticket.priority = priority;
          if (type) ticketData.ticket.type = type;
          if (assignee_id) ticketData.ticket.assignee_id = parseInt(assignee_id, 10);
          if (tags) ticketData.ticket.tags = tags;
    
          const result = await new Promise((resolve, reject) => {
            (client as any).tickets.update(parseInt(ticket_id, 10), ticketData, (error: Error | undefined, req: any, result: any) => {
              if (error) {
                console.log(error);
                reject(error);
              } else {
                resolve(result);
              }
            });
          });
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(result, null, 2)
            }]
          };
        } catch (error: any) {
          return {
            content: [{
              type: "text",
              text: `Error: ${error.message || 'Unknown error occurred'}`
            }],
            isError: true
          };
        }
      }
    );
Behavior2/5

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

With no annotations, the description carries full burden but only states it 'updates' without detailing behavioral traits. It doesn't disclose permissions needed, whether updates are reversible, rate limits, or what happens to unspecified properties (e.g., if tags replace existing ones, as hinted in schema but not description).

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, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's complexity, making it easy to parse without unnecessary elaboration.

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?

For a mutation tool with 7 parameters, no annotations, and no output schema, the description is inadequate. It lacks behavioral context (e.g., auth needs, side effects), usage guidelines, and doesn't compensate for the absence of structured fields, leaving significant gaps for an AI agent.

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 schema fully documents all 7 parameters with descriptions and enums. The description adds no additional meaning beyond implying 'properties' updates, aligning with the baseline score when schema does the heavy lifting.

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 verb ('Update') and resource ('Zendesk ticket's properties'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'zendesk_create_ticket' or 'zendesk_get_ticket' beyond the basic action, missing explicit distinction.

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. It doesn't mention prerequisites (e.g., needing a ticket ID), exclusions, or comparisons to siblings like 'zendesk_add_private_note' for adding notes versus updating properties.

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

Related 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/koundinya/zd-mcp-server'

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