Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

list_audit_logs

Read-onlyIdempotent

Retrieve paginated configuration audit logs showing admin changes with attribution. Supports filtering by source type and action for targeted audits.

Instructions

Returns instance-wide configuration audit logs as paginated skeletons (id, source_type, actor_name, action, change_description, created_at), every admin/config change with attribution. Enterprise-plan-gated; on lower plans returns upstream_error with the underlying http_status (403/404). Default limit: 100; pass cursor, fields, filter (server-side filters for source_type/action are honored). For per-ticket field changes use get_ticket_audits, this tool is admin-config only, not ticket-level.

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 audit log objects instead of the thin projection
instanceNoOverride the sticky instance for this call
filter_actionNoOptional filter[action] query (e.g. "create", "update")
filter_source_typeNoOptional filter[source_type] query (e.g. "Trigger", "User")
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, and idempotentHint. The description adds value by detailing caching behavior (stale cursor auto-reset with cursor_invalidated flag), plan-gating with HTTP status codes, and server-side filter honor. Does not contradict annotations; adds context that is not in structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is relatively long but every sentence adds value: core purpose, plan gating, defaults, pagination details, sibling distinction. It is well-structured with front-loaded purpose and subsequent behavioral details. No wasted words given the tool's complexity.

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 9 parameters, 100% schema coverage, no output schema, the description covers key behavioral aspects: caching, error handling, pagination, plan restrictions, and sibling differentiation. It lacks explicit return value structure but lists returned fields in the first sentence, which is sufficient for a read-only list tool.

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 for all 9 parameters. The description adds meaning beyond schema: default limit behavior, cursor staleness reset, fields whitelist as array, supported filter keys, refresh cache bypass, verbose mode, and optional filter queries. This enriches parameter understanding beyond the schema alone.

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 'instance-wide configuration audit logs as paginated skeletons' with specific fields listed. It distinguishes itself from the sibling tool 'get_ticket_audits' by specifying that this tool is for admin-config changes only, not ticket-level changes, making purpose and scope unambiguous.

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?

Explicitly says when to use the alternative 'get_ticket_audits' for ticket-level changes. Details plan-gating behavior (Enterprise only, returns error on lower plans) and default limit. Provides clear context for pagination and filter usage, guiding the agent on appropriate invocation scenarios.

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