Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

search

Search Zendesk tickets, users, and organizations using query parameters with sorting and pagination options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
sort_byNoField to sort by
sort_orderNoSort order (asc or desc)
pageNoPage number for pagination
per_pageNoNumber of results per page (max 100)

Implementation Reference

  • The handler function executes the search using zendeskClient.search with provided parameters and returns formatted JSON results or an error message.
    handler: async ({ query, sort_by, sort_order, page, per_page }) => {
      try {
        const params = { sort_by, sort_order, page, per_page };
        const result = await zendeskClient.search(query, params);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error searching: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the search tool: query (required string), optional sort_by, sort_order, page, per_page.
    schema: {
      query: z.string().describe("Search query string"),
      sort_by: z.string().optional().describe("Field to sort by"),
      sort_order: z.enum(["asc", "desc"]).optional().describe("Sort order (asc or desc)"),
      page: z.number().optional().describe("Page number for pagination"),
      per_page: z.number().optional().describe("Number of results per page (max 100)")
    },
  • src/server.js:47-52 (registration)
    Registration of the search tool (included in allTools via searchTools spread) using the MCP server's tool() method in a loop over all imported tools.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/JurreBrandsenInfoSupport/zendesk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server