Skip to main content
Glama

zendesk_post_comment

Post a public reply on a Zendesk ticket visible to the requester. Use for customer-facing responses.

Instructions

Post a public reply on a Zendesk ticket. The reply is visible to the requester. Use for customer-facing responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYes
bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'zendesk_post_comment' tool. Calls the shared helper _post_comment_data with public=True.
    def zendesk_post_comment(ticket_id: int, body: str) -> str:
        """Post a public reply on a Zendesk ticket. The reply is visible to the requester. Use for customer-facing responses."""
        return _post_comment_data(ticket_id, body, public=True)
  • Helper function that performs the actual Zendesk API call to post a comment or internal note on a ticket.
    def _post_comment_data(ticket_id: int, body: str, public: bool) -> str:
        try:
            client = get_client()
            ticket = Ticket(id=ticket_id)
            ticket.comment = Comment(body=body, public=public)
            client.tickets.update(ticket)
            label = "Public comment" if public else "Internal note"
            return f"{label} posted successfully on ticket #{ticket_id}."
        except ConfigError as e:
            return str(e)
        except Exception as e:
            if "RecordNotFound" in str(e) or "404" in str(e):
                return f"Ticket #{ticket_id} not found or not accessible with current credentials."
            return f"Zendesk API error: {e}"
  • Registration of the tool via the @mcp.tool() decorator inside register_write_comment_tools().
    def register_write_comment_tools(mcp) -> None:
        @mcp.tool()
        def zendesk_post_comment(ticket_id: int, body: str) -> str:
            """Post a public reply on a Zendesk ticket. The reply is visible to the requester. Use for customer-facing responses."""
            return _post_comment_data(ticket_id, body, public=True)
  • Top-level call in main() that registers the write_comment tools including zendesk_post_comment on the MCP server.
    register_write_comment_tools(mcp)
Behavior3/5

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

No annotations are provided, so the description must carry the disclosure burden. It reveals that the reply is public and visible to the requester, which is a key behavioral trait. However, it omits other important behaviors like authentication requirements, rate limits, or side effects (e.g., ticket status updates or notifications).

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 extremely concise with two short sentences. Every word adds value, and the key information is front-loaded. No redundancy or fluff.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema, the description covers the main purpose and usage. However, it could be more complete by adding behavioral details (since no annotations) and minor parameter clarifications, but overall it's solid.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate. It does not elaborate on the two parameters ('ticket_id' and 'body') beyond their names. While the parameters are straightforward, details like allowed body format (e.g., markdown) or ticket ID source are absent.

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?

The description clearly states the action ('Post a public reply'), the resource ('Zendesk ticket'), and distinguishes it from the sibling tool 'zendesk_post_internal_note' by specifying visibility and customer-facing use.

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

Usage Guidelines4/5

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

It explicitly says 'Use for customer-facing responses,' providing context for when to use. However, it does not explicitly mention when not to use or name the alternative 'zendesk_post_internal_note' directly, though the sibling list allows inference.

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