Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_organization_fields

Read-onlyIdempotent

Retrieve organization-level custom field schemas, including IDs, types, keys, and titles. Supports pagination, field filtering, and optional verbose output for dropdown options.

Instructions

Returns organization-level custom fields (the schema, not values) as paginated skeletons (id, type, key, title, active, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true for dropdown options. Note these are distinct from list_user_fields (user-level) and list_ticket_fields (ticket-level). For values on a specific organization, fetch with get_organization and read organization_fields.

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 organization-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 provide readOnlyHint, openWorldHint, idempotentHint. The description adds behavioral details about pagination (skeletons, default limit, cursor, fields, filter, verbose) and caching behavior (via schema descriptions). No contradiction with annotations. Slightly more context would be needed for a 5, but it's adequate.

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 with four sentences: purpose, key parameters, sibling distinction, and alternative usage. Every sentence serves a purpose, no redundancy, and the most critical information is front-loaded.

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 tool has 7 optional parameters, no output schema, and rich annotations, the description covers output format (skeleton fields), parameter roles, and relationships to other tools. It could mention error handling or pagination limits, but overall it is complete enough for an agent to use the tool correctly.

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 baseline is 3. The description summarizes the key parameters and their use cases (e.g., 'for dropdown options') but does not add significant meaning beyond the schema's existing descriptions. It groups them effectively but offers limited extra value.

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 organization-level custom field schemas as paginated skeletons, explicitly listing the fields included. It differentiates from sibling tools list_user_fields and list_ticket_fields, making the purpose unmistakable.

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?

The description specifies when to use this tool (schema, not values) and provides explicit alternatives: list_user_fields, list_ticket_fields for other levels, and get_organization for values. It also mentions the default limit and parameter options, giving clear usage context.

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