Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_ticket_fields

Read-onlyIdempotent

Retrieve paginated ticket fields (system and custom) with options for filtering, verbose details, and cursor-based pagination.

Instructions

Returns ticket fields (system + custom) as paginated skeletons (id, type, key, title, active, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true for full bodies including dropdown custom_field_options. For "is it safe to delete this field?" call find_field_usage, it scans every rule and form for references with why_matched breadcrumbs. For a full field hygiene report, audit_field_health bundles unused / inactive-only / empty-options / not-on-any-form checks.

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 ticket-field 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, indicating safe read behavior. The description adds valuable behavioral details: pagination with caching, default limit 100, cursor staleness auto-reset, filter ignoring unsupported keys, and projection via fields/verbose. This goes beyond the 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 two sentences: first sentence clearly states purpose and key defaults, second sentence provides alternative tools. No wasted words, front-loaded with essential information.

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, no output schema, but high schema coverage, the description covers pagination, caching, projection, filtering, and links to sibling tools for safety and hygiene. It is sufficient for an agent to use correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds contextual meaning beyond schema: default limit, cursor being opaque token from previous response, filter supported keys listed, and verbose for full objects. It also explains cache behavior and refresh parameter.

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 it returns ticket fields as paginated skeletons with specific fields, and distinguishes from sibling tools by referencing find_field_usage and audit_field_health for different purposes. The verb 'returns' and resource 'ticket fields' are specific.

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 provides alternatives for related tasks: 'For is it safe to delete this field? call find_field_usage' and 'For a full field hygiene report, audit_field_health'. It implies when to use this tool (listing fields) and when to use others, though it does not state explicit exclusions.

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