Skip to main content
Glama

Zendesk

by io.github.pipeworx-io

Zd List Tickets

zd_list_tickets
Read-onlyIdempotent

List Zendesk support tickets for the connected account, sortable by created_at, updated_at, priority, or status. Returns ticket IDs, subjects, statuses, and metadata. Supports pagination via page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
sort_byNoSort field (created_at, updated_at, priority, status)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal count of tickets
ticketsNoList of tickets
next_pageNoURL to next page

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total count of tickets",
+      "type": "number"
+    },
+    "next_page": {
+      "description": "URL to next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tickets": {
+      "description": "List of tickets",
+      "items": {
+        "properties": {
+          "created_at": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "description": {
+            "description": "Ticket description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Ticket ID",
+            "type": "number"
+          },
+          "priority": {
+            "description": "Ticket priority",
+            "type": "string"
+          },
+          "status": {
+            "description": "Ticket status",
+            "type": "string"
+          },
+          "subject": {
+            "description": "Ticket subject",
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "Last update timestamp",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "page": 1,
+    "sort_by": "updated_at"
+  },
+  {
+    "sort_by": "priority"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds value by specifying sortability, return fields (IDs, subjects, statuses, metadata), and pagination support via 'page'. No contradictions with annotations.

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 two concise sentences, with the primary action stated first. Every sentence adds value without redundancy or unnecessary detail.

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 presence of an output schema, the description adequately covers functionality (listing, sorting, pagination). It does not mention default sorting or scope limits, but these are minor given the output schema's expected role.

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 the baseline is 3. The description restates the sortable fields and pagination, but does not add new meaning beyond the schema definitions. No additional parameter constraints or formats are explained.

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 that the tool lists Zendesk support tickets for the connected account, with explicit mention of sorting options and return fields. This distinguishes it from sibling tools like zd_get_ticket (single ticket retrieval) and zd_search_tickets (search-based filtering).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies a general listing use case, it does not explicitly guide when to use this tool versus the sibling zd_search_tickets for filtered searches. The guidance is adequate but could be improved by contrasting with search capabilities.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zendesk toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) which all provide factual answers, making it unclear which to use. The set also mixes Zendesk tools with a large number of prediction market and data tools, creating confusion.

Naming Consistency2/5

Naming conventions are inconsistent: Zendesk tools use 'zd_' prefix, Pipeworx tools use various prefixes like 'ask_', 'bet_', 'compare_', etc., and some are named with full words. There is no uniform pattern across the set.

Tool Count2/5

35 tools is high for a server named 'Zendesk', especially since only 5 are Zendesk-specific. The majority are unrelated to Zendesk, indicating the tool count is inappropriate for the implied purpose.

Completeness1/5

For a Zendesk server, the tool set is severely incomplete, offering only basic CRUD operations (get, list, search for tickets and users). Missing essential Zendesk features like ticket creation, update, delete, or macros, while containing many irrelevant tools from other domains.

Resources