Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_groups

Read-onlyIdempotent

Retrieve Zendesk agent groups with pagination, field whitelisting, and filters for active status or title. Returns group id, name, description, and timestamps.

Instructions

Returns agent groups as paginated skeletons (id, name, description, default, deleted, timestamps). Default limit: 100; pass cursor, fields, filter, or verbose: true. Group lists are typically small (dozens), so this is usually fine to call without filtering. For "is it safe to delete this group?" call find_group_usage, it scans triggers, automations, views, and SLA policies for references with why_matched breadcrumbs.

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 group 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 readOnly and idempotent hints. The description adds behavioral details: pagination with default limit 100, server-side caching with stale cursor auto-reset, field filtering, verbose mode, and cache bypass via refresh. No contradiction with 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?

The description is a single compact paragraph with no wasted words. The core purpose and key parameters are front-loaded, and the alternative tool call is highlighted with bold text.

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 complexity (7 parameters, no output schema), the description covers return structure, pagination, caching, filtering, and usage guidance. Minor omission: the `default` field in the skeleton is not explained. Overall, sufficient for an agent to use the tool.

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 the baseline is 3. The description adds minimal extra context beyond the schema, such as the default limit and cursor auto-reset behavior, but mostly reiterates param usage. No significant value added over schema 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 clearly states the verb 'returns' and the resource 'agent groups', specifies the skeleton fields, and distinguishes from sibling tool `find_group_usage` by noting when to use that instead.

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 explicitly recommends calling `find_group_usage` when checking deletion safety, providing an alternative. It also notes the typical small size of group lists, implying that filtering is often unnecessary. However, it could be more explicit about 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/rlowndes9/zendesk-mcp-server'

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