Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_agent_skill_assignments

Read-onlyIdempotent

Retrieve the skills and queues assigned to a Zendesk agent via user ID, returned as paginated routing-attribute values.

Instructions

Returns the routing-attribute values an agent holds (i.e. which skills/queues that user is eligible for) as paginated skeletons. Backed by /api/v2/users/{user_id}/instance_values.json, the canonical SBR-assignment endpoint. Plan-gated, degrades to upstream_error when omnichannel routing is off. Scope-gated because it touches user data (config_plus_audits or full). For attribute/value catalogs (not assignments), use list_routing_attributes / list_routing_attribute_values.

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
user_idYesAgent (Zendesk user) ID
verboseNoReturn full value objects
instanceNoOverride the sticky instance
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds useful context: paginated skeletons, plan-gated behavior (upstream_error), scope-gated, cache/cursor behavior. No contradictions. A 4 is appropriate as it adds significant value 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?

Approximately 4 sentences, front-loaded with purpose, then API backing, constraints, and alternatives. No wasted words.

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?

Covers purpose, API endpoint, plan/scope gating, pagination, caching, parameter behaviors, and alternatives. Could mention response shape slightly more, but overall very complete for a list tool with no output schema.

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 coverage, baseline is 3. Description adds substantial meaning for many parameters: explains limit scoping, cursor staleness, field whitelisting, filter options, cache bypass, etc. Greatly enhances agent understanding.

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?

Description clearly states verb (returns) and resource (routing-attribute values an agent holds) and explicitly distinguishes from sibling tools list_routing_attributes and list_routing_attribute_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?

Describes when to use (for agent assignments) and when not to (for catalogs), provides alternatives, and mentions plan/scope gating constraints.

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