Skip to main content
Glama
benpalmer1

Gorgias MCP Server

by benpalmer1

List Events

gorgias_list_events
Read-only

Retrieve paginated lists of Gorgias events, filterable by object, user, type, and creation date range to track helpdesk activity.

Instructions

GET /api/events — List events, cursor-paginated and ordered by creation date (most recent first). Supports filtering by object, user, event type, and creation datetime range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return per page (1-100, default 30)
typesNoFilter events by event type names. The Gorgias API expects an array of strings. Common values include 'ticket-created', 'ticket-updated', 'ticket-deleted', 'ticket-message-created', 'customer-created', etc. — there are 100+ possible values; see the Gorgias Event Object documentation for the full list.
cursorNoPagination cursor. Pass the value of next_cursor from a previous response to retrieve the next page
order_byNoSort order (default: 'created_datetime:desc')
user_idsNoFilter events by the IDs of the users who triggered them. The Gorgias API expects an array of integers.
object_idNoFilter events by the ID of the associated object (e.g., ticket ID, customer ID)
object_typeNoFilter events by the type of the associated object. The API requires object_id when object_type is provided.
created_datetimeNoFilter events by creation datetime. Object of comparator -> ISO 8601 datetime, e.g. { gte: '2026-01-01T00:00:00Z', lt: '2026-02-01T00:00:00Z' }.
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds cursor pagination and default ordering context. However, it does not mention response format, rate limits, or behavior beyond what annotations already imply.

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 concise, containing only two sentences that immediately state the endpoint, purpose, and key behaviors. Every phrase adds value, with no redundancy.

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 rich schema and annotations, the description covers the essential behavior for a list tool. It could explicitly mention response shape (e.g., next_cursor), but the cursor parameter description compensates, making it nearly complete.

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 provides 100% coverage with detailed descriptions for all 8 parameters. The description simply summarizes the filterable fields without adding new meaning or relationships 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 clearly states it lists events, with the exact endpoint, pagination behavior, and supported filters. This distinctly sets it apart from gorgias_get_event, which retrieves a single event.

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?

No guidance is provided on when to use this tool versus alternatives like gorgias_get_event or other list tools. It only describes what it does, without stating scenarios, prerequisites, or exclusions.

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