Skip to main content
Glama

zendesk_search

Read-onlyIdempotent

Search Zendesk records using a query DSL to filter tickets by status, priority, type, and other fields, returning matching results for targeted workflows.

Instructions

Search Zendesk with the query DSL (e.g. 'type:ticket status:open priority:urgent').

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>",
      "query": "<query>"
    },
    "name": "zendesk_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesAgent email address
queryYesZendesk search query
api_tokenYesZendesk API token
subdomainYesZendesk subdomain (e.g. mycompany)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the DSL syntax which is useful, but says nothing about auth mechanism, rate limits, pagination, or result shape beyond what annotations provide.

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?

A single tight sentence with the actionable DSL example front-and-center and zero filler.

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?

Annotations carry the safety profile, schema documents all params, and no output schema exists to explain. The description plus example is largely sufficient for correct invocation, with only deeper DSL coverage and result behavior left unstated.

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% so the baseline is 3, but the description adds genuine meaning for the query parameter by showing DSL syntax the schema only calls 'Zendesk search query'. The example materially helps construct a valid query.

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?

Clear verb+resource: 'Search Zendesk' with a concrete DSL example ('type:ticket status:open priority:urgent'). It distinguishes search from sibling list/get_ticket actions implicitly, though it never names them to sharpen the boundary.

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?

The DSL example implies you use this for filtered/query-based lookups, but there's no explicit when-to-use vs zendesk_list_tickets or zendesk_get_ticket, and no exclusions or preconditions stated.

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