Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_brands

Read-onlyIdempotent

List all Zendesk brands with essential fields (id, name, subdomain, active, default). Supports pagination, filtering, and custom field selection for efficient brand enumeration.

Instructions

Returns brands as paginated skeletons (id, name, subdomain, active, default, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true. Plan-gated, multi-brand requires the appropriate Zendesk plan; on single-brand instances you'll see a single default brand. Brand lists are tiny, straight enumeration is fine.

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 brand 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?

Adds behavioral details beyond annotations: plan-gating, pagination, projection options. Annotations already indicate readOnly, idempotent, openWorld; description does not contradict.

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?

Three concise sentences, front-loaded with purpose, 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?

Explains return value (skeleton fields), pagination, plan-gating. Without output schema, covers essentials; could mention pagination token in response explicitly.

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%, baseline 3. Description summarizes key parameters and default limit but adds limited new meaning beyond schema.

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?

Clearly states returns brands as paginated skeletons with specific fields. Distinguishes from sibling 'list_' tools by mentioning plan-gating and that brand lists are tiny, straight enumeration is fine.

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 context on plan-gating and that enumeration is fine, but does not explicitly compare to alternatives like get_brand or other list tools.

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