Skip to main content
Glama
koundinya

Zendesk MCP Server

by koundinya

zendesk_add_private_note

Add a private internal note to a Zendesk ticket using the ticket ID. This tool enables internal communication within the Zendesk ticketing system without sharing details externally.

Instructions

Add a private internal note to a Zendesk ticket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesThe content of the private note
ticket_idYesThe ID of the ticket to add a note to

Implementation Reference

  • The handler function that implements the tool logic: updates the Zendesk ticket with a private note using the node-zendesk client.
    async ({ ticket_id, note }) => {
      try {
        const result = await new Promise((resolve, reject) => {
          (client as any).tickets.update(parseInt(ticket_id, 10), {
            ticket: {
              comment: {
                body: note,
                public: false
              }
            }
          }, (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 for the tool parameters: ticket_id and note.
    {
      ticket_id: z.string().describe("The ID of the ticket to add a note to"),
      note: z.string().describe("The content of the private note")
    },
  • MCP server tool registration call within zenDeskTools function.
    server.tool(
      "zendesk_add_private_note",
      "Add a private internal note to a Zendesk ticket",
      {
        ticket_id: z.string().describe("The ID of the ticket to add a note to"),
        note: z.string().describe("The content of the private note")
      },
      async ({ ticket_id, note }) => {
        try {
          const result = await new Promise((resolve, reject) => {
            (client as any).tickets.update(parseInt(ticket_id, 10), {
              ticket: {
                comment: {
                  body: note,
                  public: false
                }
              }
            }, (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
          };
        }
      }
    );
  • Shared Zendesk API client initialized from environment variables, used by the tool handler.
    const client = zendesk.createClient({
      username: process.env.ZENDESK_EMAIL as string,
      token: process.env.ZENDESK_TOKEN as string,
      remoteUri: `https://${process.env.ZENDESK_SUBDOMAIN}.zendesk.com/api/v2`,
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Add' implies a write operation, it doesn't specify whether this requires special permissions, if notes are editable/deletable, rate limits, or what happens on success/failure. The description is minimal and lacks critical behavioral context for a mutation tool.

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 that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded and wastes no space.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, permission requirements, or how it differs from similar tools. Given the complexity of ticket management systems, more context is needed.

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?

The schema description coverage is 100%, with both parameters ('ticket_id' and 'note') clearly documented in the schema. The description doesn't add any additional parameter semantics beyond what's already in the schema, so the baseline score of 3 is appropriate.

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 ('Add') and resource ('private internal note to a Zendesk ticket'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'zendesk_add_public_note', which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'zendesk_add_public_note' or 'zendesk_update_ticket'. There's no mention of prerequisites, permissions needed, or contextual constraints for adding private notes.

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