Skip to main content
Glama
Sign In
Zendesk MCP Server by Fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add Public Comment

add_public_comment

Add a public comment (visible to requester) to a ticket, optionally with file attachments (uploaded via the Zendesk Uploads API and carried on the comment).

Instructions

Add a public comment (visible to requester) to a ticket, optionally with file attachments (uploaded via the Zendesk Uploads API and carried on the comment). The comment is appended to the ticket thread and emails the requester; use add_private_note instead for an internal, agent-only note.

Input Schema

NameRequiredDescriptionDefault
bodyYesComment text sent to the requester. Plain text or HTML; visible in the ticket.
ticket_idYesTicket ID — the numeric id of the ticket to reply on. Obtain it from search_tickets or list_tickets.
attachmentsNoFiles to attach to this comment (base64-encoded content).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.1
    • addedInput schema / properties / attachments / items / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.24.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv2.22.0
    • addedInput schema / properties / attachments / items / properties / file_base64 / contentEncoding
      Added value: +"base64"
  4. Changed2 schema fields changedv2.20.2
    • changedInput schema / properties / attachments / items / properties / file_base64 / description
      Previous value: -"File content encoded as base64."New value: +"File content encoded as base64. At most 10420224 characters (about 7.45 MB of file), and the attachments of one call must stay under that total; the HTTP transport additionally caps request bodies at 4 MB."
    • addedInput schema / properties / attachments / items / properties / file_base64 / maxLength
      Added value: +10420224
  5. Changed2 schema fields changedv2.6.0
    • changedInput schema / properties / body / description
      Previous value: -"Comment content"New value: +"Comment text sent to the requester. Plain text or HTML; visible in the ticket."
    • changedInput schema / properties / ticket_id / description
      Previous value: -"Ticket ID"New value: +"Ticket ID — the numeric id of the ticket to reply on. Obtain it from search_tickets or list_tickets."
  6. Changed1 schema field changedv2.4.1
    • addedInput schema / properties / attachments
      Added value: +{
+  "description": "Files to attach to this comment (base64-encoded content).",
+  "items": {
+    "properties": {
+      "content_type": {
+        "default": "application/octet-stream",
+        "description": "MIME type, e.g. \"text/plain\", \"image/png\", \"application/pdf\".",
+        "minLength": 1,
+        "type": "string"
+      },
+      "file_base64": {
+        "description": "File content encoded as base64.",
+        "format": "base64",
+        "minLength": 1,
+        "pattern": "^$|^(?:[0-9a-zA-Z+/]{4})*(?:(?:[0-9a-zA-Z+/]{2}==)|(?:[0-9a-zA-Z+/]{3}=))?$",
+        "type": "string"
+      },
+      "file_name": {
+        "description": "File name, e.g. \"app.log\" or \"screenshot.png\".",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "file_name",
+      "file_base64"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  7. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  8. First observedv1.7.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, idempotent=false, openWorld=true, but the description adds traits annotations cannot convey: the comment emails the requester, is appended to the ticket thread, and attachments are uploaded via the Zendesk Uploads API. It does not mention auth requirements or rate limits, so it stops short of a 5.

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 sentences, zero waste; the core action and visibility are front-loaded before the attachment mechanism and the sibling alternative.

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

Completeness5/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 output schema, the description supplies the missing behavioral context (email side effect, thread append, sibling routing) and the schema fully covers parameters. Nothing an agent needs to call it correctly is absent.

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?

Schema coverage is 100%, so the schema already documents all three parameters and the 3 baseline applies. The description goes slightly beyond by explaining the attachment mechanism (Uploads API, carried on the comment), which clarifies the otherwise opaque base64 payload.

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?

States a specific verb+resource (add a public comment) with scope (visible to requester, on a ticket) and explicitly distinguishes itself from the sibling add_private_note. An agent can tell it apart from the internal-note tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use (public comment visible to requester) and names the correct alternative with the condition that selects it (use add_private_note for an internal, agent-only note). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools