Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_automations

Read-onlyIdempotent

Retrieve Zendesk automations (time-based rules) with pagination, filtering, and optional full object details. Ideal for auditing automation configurations.

Instructions

Returns automations (time-based rules) as paginated skeletons (id, title, active, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true. Automation firing data is not exposed by the Zendesk API on standard plans, so find_unused returns indeterminate for automations rather than guessing. For tag / field reference questions across automations + triggers + macros, prefer find_field_usage or audit_tag_sprawl.

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
verboseNoReturn full automation objects instead of the thin projection
instanceNoOverride the sticky instance for this call
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavior details: pagination with cursor and caching, default limit, and that firing data is not exposed on standard plans. No rate limit or auth information, but sufficient beyond annotations.

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?

Three sentences, front-loaded with core purpose, then key options, then limitations and alternatives. Every sentence adds value without 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 7 parameters and no output schema, the description explains pagination, caching, and limitations. Points to sibling tools for related tasks. Could include more on filter object semantics, but schema covers that. Adequate for agent selection and invocation.

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?

Schema coverage is 100%, so baseline is 3. The description reiterates default limit and mentions optional parameters like cursor, fields, filter, verbose. It adds context about cursor staleness and caching but does not significantly enhance meaning beyond the schema's own descriptions.

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 explicitly states it returns automations (time-based rules) as paginated skeletons with specific fields (`id`, `title`, `active`, `updated_at`). It distinguishes from siblings like `get_automation` (single) and `find_unused` (indeterminate for automations).

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

Usage Guidelines5/5

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

Provides clear guidance on when to use alternatives: 'For tag / field reference questions across automations + triggers + macros, prefer `find_field_usage` or `audit_tag_sprawl`.' It also notes that firing data is not exposed, so `find_unused` returns `indeterminate` for automations.

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