Skip to main content
Glama
forterro

freshservice-mcp

by forterro

manage_ticket_conversation

Reply to customer tickets, add internal notes, update conversation details, or list existing threads to keep support workflows on track.

Instructions

Manage ticket conversations — replies, notes, updates.

    Args:
        action: 'reply', 'add_note', 'update', 'list'
        ticket_id: Required for reply, add_note, list
        conversation_id: Required for update
        body: HTML body content (reply, add_note, update)
        from_email: Sender email (reply)
        user_id: Agent user ID (reply)
        cc_emails: CC email list (reply)
        bcc_emails: BCC email list (reply)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
actionYes
user_idNo
cc_emailsNo
ticket_idNo
bcc_emailsNo
from_emailNo
conversation_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

There are no annotations, so the description must disclose side effects. It fails to mention that replies send emails or that updates modify existing conversations, nor does it discuss permissions or reversibility. It only notes that body is HTML, which is a format detail, not a behavioral trait.

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 summary line followed by a compact arg list. It is well-structured, front-loaded with the purpose, and every line provides actionable information.

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?

The description covers all the main operational aspects of the tool, including action-specific parameters. It does not discuss return values, but the presence of an output schema mitigates this. It also doesn't mention error handling or edge cases, but these are less critical given the clear action breakdown.

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

Parameters5/5

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

With no schema descriptions, the description is essential. It comprehensively explains each parameter's purpose and its applicability to specific actions, filling the gap left by the schema's 0% coverage.

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 tool manages ticket conversations, and enumerates the supported actions (reply, add_note, update, list). This distinguishes it from sibling tools like manage_ticket, which focuses on ticket-level operations.

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?

The description provides action-specific parameter requirements, indicating when each action is appropriate (e.g., reply requires ticket_id, from_email, etc.). However, it doesn't explicitly compare to alternative tools or state when not to use this tool.

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/forterro/freshservice_mcp'

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