Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

list_users

Retrieve and filter Zendesk user accounts by role with pagination controls for efficient user management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
per_pageNoNumber of users per page (max 100)
roleNoFilter users by role

Implementation Reference

  • The handler function for the 'list_users' tool. It constructs parameters from input, calls zendeskClient.listUsers, formats the result as JSON text response or error message.
    handler: async ({ page, per_page, role }) => {
      try {
        const params = { page, per_page, role };
        const result = await zendeskClient.listUsers(params);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error listing users: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining optional input parameters for the list_users tool: page, per_page, and role.
    schema: {
      page: z.number().optional().describe("Page number for pagination"),
      per_page: z.number().optional().describe("Number of users per page (max 100)"),
      role: z.enum(["end-user", "agent", "admin"]).optional().describe("Filter users by role")
    },
  • src/server.js:48-52 (registration)
    Generic registration loop that registers all tools, including 'list_users' from usersTools, with the MCP server using server.tool().
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • ZendeskClient helper method that performs the actual API GET request to /users.json with pagination/filter params.
    async listUsers(params) {
      return this.request("GET", "/users.json", null, params);
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