Skip to main content
Glama

zendesk_list_tickets

Read-onlyIdempotent

Lists recent Zendesk tickets and flags any that are still new, so agents can review incoming support requests and prioritize follow-up.

Instructions

List recent Zendesk tickets (signals when any are still new).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subdomain": "<subdomain>",
      "email": "<email>",
      "api_token": "<api_token>"
    },
    "name": "zendesk_list_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesAgent email address
limitNoTickets to return (max 100, default 25)
sort_byNoSort field (e.g. created_at, updated_at)
api_tokenYesZendesk API token
subdomainYesZendesk subdomain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only the ambiguous parenthetical "signals when any are still new", which hints at some status output but doesn't say what signal, in what field, or what counts as "new".

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?

A single short sentence with the resource front-loaded and zero padding. It is efficient, though the vague parenthetical is the one phrase that doesn't fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter tool requiring subdomain, email and API token, the description says nothing about authentication expectations, pagination, or what the returned list looks like. The schema covers parameters, but with no output schema the description should have done more to describe the return payload.

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 coverage is 100%, so limit, sort_by and the three credential fields are already documented in the schema. The description adds no syntax, defaults, or credential-acquisition detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List recent Zendesk tickets") with a recency scope, which distinguishes it from an unconstrained search. However, it never names the obvious siblings (zendesk_search, zendesk_get_ticket) that an agent would weigh it against.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance; the agent must infer from the word "recent" that this is a quick overview rather than a filtered query. Nothing tells the caller to prefer zendesk_search for filters or zendesk_get_ticket for a specific ID.

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

Deploy Server

Other Tools