Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_dynamic_content

Read-onlyIdempotent

List localizable snippets used in macros, triggers, and automations. Returns paginated skeletons or full objects with variants; supports filtering and cursor-based pagination.

Instructions

Returns dynamic content items (the localizable snippets used in macros, triggers, automations) as paginated skeletons (id, name, default_locale_id, variants_count, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true to inline variant bodies per locale. Plan-gated, Professional+; degrades to upstream_error on lower plans. Cross-reference variant locales with list_locales to spot missing translations.

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 dynamic content objects (with variants) instead of the thin projection
instanceNoOverride the sticky instance for this call
Behavior5/5

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

Adds important behavioral details beyond annotations: plan-gating (Professional+, degrades to 'upstream_error'), cursor auto-reset on stale cursors, and server-side caching. Annotations declare readOnlyHint, openWorldHint, idempotentHint, which are consistent with the description.

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 at 4 sentences, front-loaded with the core purpose and behavior. Every sentence adds value without redundancy.

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?

Despite no output schema, the description explains the return structure for both thin and verbose modes, cursor and error behavior, and ties to other tools (list_locales). It is comprehensive for a list tool.

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 description coverage is 100%, so baseline is 3. The tool description provides a high-level summary of parameters (defaults, usage patterns) but adds no new semantic details beyond the schema's parameter 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?

The description clearly states 'Returns dynamic content items' with a specific verb and resource, explaining what dynamic content is (localizable snippets) and the output format (paginated skeletons with specific fields). This distinguishes it from other list tools.

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?

Provides guidance on when to use (e.g., passing 'verbose: true' for full objects) and cross-referencing with 'list_locales'. However, it does not explicitly contrast with alternatives like 'get_dynamic_content' or state when not to use it.

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