Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_chats

Read-onlyIdempotent

List Zendesk Chat conversations with pagination. Use cursor, fields, and filter parameters to refine results.

Instructions

List Zendesk Chat conversations as paginated items in their native shape (no skeleton projection, chat payloads are already compact). Default limit: 100; pass cursor, fields, or filter. Plan-gated, degrades to upstream_error on instances without the Chat add-on. Scope-gated when chats include user/ticket data (config_plus_audits or full).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return. Default 100. The full corpus is fetched and cached server-side; this only limits what the response carries.
cursorNoOpaque pagination token from a previous response. Slices the next page from the cached corpus. Stale cursors (older than the cache TTL) auto-reset to offset 0 and set cursor_invalidated: true.
fieldsNoWhitelist of field names. Overrides the default projection. Use to opt into extra fields (e.g. ["id","title","active","position","category_id","updated_at"]) without going fully verbose.
filterNoStructured filter applied to the cached corpus before slicing. Supported keys: active (bool), category_id (number/string), title_contains (string, case-insensitive), updated_since (ISO timestamp). Unsupported keys are ignored with a note in the response.
refreshNoBypass cache and re-fetch from Zendesk
instanceNoOverride the sticky instance for this call
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds critical behavioral traits: plan-gating (degrading to upstream_error without Chat add-on) and scope-gating (when chats include user/ticket data). This goes beyond annotations and helps the agent understand constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with two sentences, no fluff. However, it uses technical jargon like 'skeleton projection' and 'Plan-gated' which may hinder readability for some agents. Still, it efficiently conveys key information.

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

Completeness3/5

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

The description lacks details about the return value shape beyond 'native shape'. Since there is no output schema, the description should provide more context about what fields or structure to expect. The parameter descriptions are complete, but the response format is underspecified.

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?

Input schema has 100% coverage with detailed descriptions for each parameter. The description only mentions 'limit', 'cursor', 'fields', and 'filter' as options, adding no new semantics beyond the schema. Baseline of 3 is appropriate.

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 lists Zendesk Chat conversations as paginated items in their native shape, distinguishing it from other list tools that target different resources (e.g., tickets, users). The mention of 'no skeleton projection' and 'compact chat payloads' further clarifies the resource specifics.

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 context on pagination, default limit, and options to pass cursor/fields/filter. It also mentions plan-gating (requires Chat add-on) and scope-gating, which imply when to use. However, it does not explicitly state when not to use or compare to sibling tools like list_tickets.

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/rlowndes9/zendesk-mcp-server'

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