Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_users

Read-onlyIdempotent

Retrieve paginated user data with basic fields (id, name, email, role). Supports cursor, field whitelisting, and structured filters for efficient enumeration.

Instructions

Returns users as paginated skeletons (id, name, email, role, organization_id, active, timestamps). Default limit: 100; pass cursor, fields, filter, or verbose: true. Scope-gated, requires config_plus_audits or full; on config returns scope_blocked. For finding a specific user prefer search (e.g. type:user email:foo@bar.com), full enumeration on a large customer base is rarely the right call. For an agent's SBR skill values, use list_agent_skill_assignments.

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 user 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?

Discloses pagination behavior (default limit, cursor, cache), scope gating, and caching details. Annotations already provide readOnlyHint, openWorldHint, idempotentHint; description adds valuable context without contradicting 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?

A single, well-structured paragraph that front-loads the main purpose and then provides essential details. Every sentence adds value, no filler.

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

Completeness5/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 comprehensively covers return format (fields, projection), pagination (cursor, limit), caching, scope restrictions, and alternatives. Complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the description adds significant meaning: explains cursor staleness, filter supported keys (active, category_id, title_contains, updated_since), verbose vs thin projection, and caching behavior. Goes well 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?

Clearly states that the tool returns paginated user skeletons with specific fields. Differentiates itself from sibling tools like 'search' (for finding specific users) and 'list_agent_skill_assignments' (for skill values).

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?

Explicitly advises when to use 'search' instead of full enumeration, and states scope requirements ('config_plus_audits' or 'full', with 'config' returning 'scope_blocked'). Provides clear guidance on appropriate usage.

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