Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_routing_attribute_values

Read-onlyIdempotent

Get paginated values for a routing attribute, e.g., skills under a skill attribute. Returns ID, name, and update time.

Instructions

Returns the values defined under one routing attribute (e.g. the actual skills under a "Skill" attribute) as paginated skeletons (id, attribute_id, name, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true. Plan-gated, degrades to upstream_error when omnichannel routing is off. To see which agents have a given value, use list_agent_skill_assignments per agent.

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
verboseNoReturn full value objects
instanceNoOverride the sticky instance
attribute_idYesParent routing attribute ID
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. The description adds useful behavioral context: pagination details (default limit, cursor behavior, caching), plan-gating, and the ability to use fields, filter, verbose, refresh. No contradictions.

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, consisting of two well-structured sentences. It front-loads the main purpose and includes key details 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 the complexity (8 parameters, no output schema), the description covers the core behavior, pagination, caching, plan-gating, and an alternative tool. It does not explain return values, but that is acceptable as per rules since no output schema exists.

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% with detailed parameter descriptions. The description adds only a high-level overview (e.g., default limit, cursor usage). It does not provide new semantic meaning beyond what the schema already offers, so the baseline score 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 returns values under a routing attribute as paginated skeletons, and it distinguishes from the sibling tool list_agent_skill_assignments by mentioning its use case for seeing which agents have a given value.

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 a clear use case and suggests an alternative tool (list_agent_skill_assignments). It also notes the plan-gating and degradation condition, giving context for when the tool may not work. However, it does not explicitly state 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