Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

update_ticket

Modify Zendesk support tickets by updating subject, priority, status, assignee, comments, tags, or type to manage customer issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTicket ID to update
subjectNoUpdated ticket subject
commentNoInternal (non-public) comment to add
priorityNoUpdated ticket priority
statusNoUpdated ticket status
assignee_idNoUser ID of the new assignee
group_idNoNew group ID for the ticket
typeNoUpdated ticket type
tagsNoUpdated tags for the ticket

Implementation Reference

  • The primary handler function implementing the 'update_ticket' tool logic. It prepares the ticket update data (conditionally including fields and ensuring internal comments) and calls the zendeskClient to perform the update.
    handler: async ({
      id,
      subject,
      comment,
      priority,
      status,
      assignee_id,
      group_id,
      type,
      tags,
    }) => {
      try {
        const ticketData = {};
    
        if (subject !== undefined) ticketData.subject = subject;
        if (comment !== undefined) {
          ticketData.comment = {
            body: comment,
            public: false, // Always internal
          };
        }
        if (priority !== undefined) ticketData.priority = priority;
        if (status !== undefined) ticketData.status = status;
        if (assignee_id !== undefined) ticketData.assignee_id = assignee_id;
        if (group_id !== undefined) ticketData.group_id = group_id;
        if (type !== undefined) ticketData.type = type;
        if (tags !== undefined) ticketData.tags = tags;
    
        const result = await zendeskClient.updateTicket(id, ticketData);
    
        return {
          content: [
            {
              type: "text",
              text: `Ticket updated successfully!\n\n${JSON.stringify(
                result,
                null,
                2
              )}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            { type: "text", text: `Error updating ticket: ${error.message}` },
          ],
          isError: true,
        };
      }
    },
  • Zod schema defining the input parameters and validation for the 'update_ticket' tool.
    schema: {
      id: z.number().describe("Ticket ID to update"),
      subject: z.string().optional().describe("Updated ticket subject"),
      comment: z
        .string()
        .optional()
        .describe("Internal (non-public) comment to add"),
      priority: z
        .enum(["urgent", "high", "normal", "low"])
        .optional()
        .describe("Updated ticket priority"),
      status: z
        .enum(["new", "open", "pending", "hold", "solved", "closed"])
        .optional()
        .describe("Updated ticket status"),
      assignee_id: z
        .number()
        .optional()
        .describe("User ID of the new assignee"),
      group_id: z.number().optional().describe("New group ID for the ticket"),
      type: z
        .enum(["problem", "incident", "question", "task"])
        .optional()
        .describe("Updated ticket type"),
      tags: z
        .array(z.string())
        .optional()
        .describe("Updated tags for the ticket"),
    },
  • src/server.js:47-52 (registration)
    The registration loop that adds the 'update_ticket' tool (included in allTools via ticketsTools) to the MCP server using server.tool().
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Supporting helper method in ZendeskClient that performs the actual API PUT request to update a ticket.
    async updateTicket(id, data) {
      return this.request("PUT", `/tickets/${id}.json`, {
        ticket: data,
        public: false,
      });
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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