Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

list_organizations

Retrieve a paginated list of organizations from Zendesk to manage customer data, with options to control page number and results per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
per_pageNoNumber of organizations per page (max 100)

Implementation Reference

  • The MCP tool handler function for 'list_organizations' that prepares parameters, calls the Zendesk client, and returns the result as JSON or an error message.
    handler: async ({ page, per_page }) => {
      try {
        const params = { page, per_page };
        const result = await zendeskClient.listOrganizations(params);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error listing organizations: ${error.message}` }],
          isError: true
        };
      }
  • Zod schema defining optional input parameters 'page' and 'per_page' for pagination.
    schema: {
      page: z.number().optional().describe("Page number for pagination"),
      per_page: z.number().optional().describe("Number of organizations per page (max 100)")
    },
  • src/server.js:47-52 (registration)
    Loop that registers all tools, including 'list_organizations', with the MCP server by calling server.tool() for each.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Definition and export of the organizationsTools array containing the 'list_organizations' tool specification.
    export const organizationsTools = [
      {
        name: "list_organizations",
        description: "List organizations in Zendesk",
        schema: {
          page: z.number().optional().describe("Page number for pagination"),
          per_page: z.number().optional().describe("Number of organizations per page (max 100)")
        },
        handler: async ({ page, per_page }) => {
          try {
            const params = { page, per_page };
            const result = await zendeskClient.listOrganizations(params);
            return {
              content: [{ 
                type: "text", 
                text: JSON.stringify(result, null, 2)
              }]
            };
          } catch (error) {
            return {
              content: [{ type: "text", text: `Error listing organizations: ${error.message}` }],
              isError: true
            };
          }
        }
      },
  • ZendeskClient method that performs the HTTP GET request to /organizations.json endpoint with provided parameters.
    async listOrganizations(params) {
      return this.request("GET", "/organizations.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