Skip to main content
Glama
benpalmer1

Gorgias MCP Server

by benpalmer1

Update Message

gorgias_update_message
Idempotent

Update a specific message within a Gorgias ticket by providing ticket ID, message ID, channel, sender type, and source. Use action parameter to force, retry, or cancel failed external actions.

Instructions

PUT /api/tickets/{ticket_id}/messages/{id} — Update an existing ticket message. channel, from_agent, and via are required. Returns 202 Accepted with the full updated TicketMessage object. Use the action query param to handle recovery from failed external actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the message to update
viaYesHow the message was received or sent from Gorgias
metaNoCustom structured metadata
actionNoPolicy for failed external actions: 'force' bypasses and continues, 'retry' retries the failed action, 'cancel' deletes the message
publicNoWhether the message is visible to customers. Set to false for internal notes.
senderNoThe person who sent the message (user or customer). Object with id (integer) and/or email (string). Example: {"id": 93}
sourceNoRouting information for the message. Object with fields: type (string, e.g. 'email'), from ({address, name}), to ([{address, name}]), cc ([{address, name}]), bcc ([{address, name}]). Example: {"type": "email", "from": {"address": "sender@example.com", "name": "Sender Doe"}, "to": [{"address": "receiver@example.com", "name": "Receiver Doe"}]}
channelYesThe channel used to send the message
headersNoMessage headers as key-value pairs (primarily for email)
subjectNoThe subject line of the message
receiverNoThe primary receiver of the message (user or customer). Optional for internal notes. Object with id (integer) and/or email (string). Example: {"id": 8} or {"email": "john@example.com"}
body_htmlNoThe full HTML version of the message body
body_textNoThe full plain-text version of the message body
ticket_idYesThe ID of the ticket associated with the message
from_agentYestrue if the message was sent by your company (agent), false if sent by a customer
message_idNoID of the message on the originating service (email ID, Messenger message ID, etc.)
attachmentsNoList of file attachments. Each item: url (required), content_type (required), name (required), size (integer|null), public (boolean), extra (object).
external_idNoID of the message in a foreign system (Aircall, Zendesk, etc.)
mention_idsNoList of User IDs to mention in an internal note
sent_datetimeNoISO 8601 datetime when the message was sent. If omitted, Gorgias manages the send lifecycle.
integration_idNoID of the integration used to send the message
failed_datetimeNoISO 8601 datetime when the message failed to be sent
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it specifies the return status (202 Accepted), the full updated TicketMessage object, and the role of the action param. Annotations already cover read-only/idempotent/open-world hints, and there is no contradiction.

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 three succinct sentences, front-loaded with the operation and resource, and each sentence provides key information without 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?

For a complex 22-parameter mutation tool with no output schema, the description covers the essential context: purpose, required fields, return value, and a notable edge case (action param). The comprehensive schema and annotations fill in the remaining details.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds value by highlighting the action param's purpose (recovery from failed external actions) and reiterating the required fields, giving a slight boost beyond the schema.

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 states the exact operation ('Update an existing ticket message') with the HTTP method and resource path. This clearly distinguishes it from sibling tools like gorgias_create_message, gorgias_get_message, and gorgias_delete_message.

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 clearly implies usage for modifying an existing ticket message and adds a specific usage note for the action query param to handle recovery from failed external actions. However, it does not explicitly state when not to use the tool or name alternative tools.

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/benpalmer1/Gorgias-MCP-Server'

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