Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_views

Read-onlyIdempotent

List Zendesk views with paginated results. Supports filtering by active status, category, title, and update time; limit and cursor for pagination.

Instructions

Returns views as paginated skeletons (id, title, active, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true. For "which views are unused?" call find_unused with kind: "views", it uses Zendesk's usage_30d to give a confident answer. For impact analysis on a field/form/group referenced by views, use find_field_usage / find_form_usage / find_group_usage.

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 view objects 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?

The description discloses significant behavioral traits beyond annotations: pagination with cursor and caching, default limit, filter supported keys, ability to bypass cache with refresh, and behavior of stale cursors. Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and the description adds rich context without any contradictions.

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 extremely concise with three sentences. The main purpose is front-loaded in the first sentence. Every sentence serves a purpose: main action, parameter/usage hints, and alternatives. No unnecessary 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?

Given 7 parameters, no output schema, the description covers return format (skeletons), default limit, caching, cursor handling, and filter keys. However, it does not describe the pagination response structure (e.g., how to get next page) or the full view object format in verbose mode, which are minor gaps. Still, it is mostly complete.

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 coverage is 100% with descriptions, but the description adds usage patterns like using fields to opt into extra fields without going fully verbose and lists supported filter keys. This provides additional context beyond the schema, justifying a score above baseline 3.

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 views as paginated skeletons, listing specific fields. It also distinguishes from sibling tools by explicitly directing users to find_unused for unused views and find_field_usage etc. for impact analysis. The verb 'returns' and resource 'views' 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 provides clear guidance on when to use alternative tools (find_unused for unused views, find_field_usage for impact analysis). However, it does not explicitly state when list_views should be chosen over other listing tools, though the context implies general listing of views. No exclusions or when-not-to-use are given.

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