Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_organization

Create a new organization in Zendesk with name, domain names, details, notes, and tags for customer support management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOrganization name
domain_namesNoDomain names for the organization
detailsNoDetails about the organization
notesNoNotes about the organization
tagsNoTags for the organization

Implementation Reference

  • The MCP tool handler for 'create_organization'. Prepares organization data from inputs and delegates to zendeskClient.createOrganization, returning formatted success/error content.
    handler: async ({ name, domain_names, details, notes, tags }) => {
      try {
        const orgData = {
          name,
          domain_names,
          details,
          notes,
          tags
        };
        
        const result = await zendeskClient.createOrganization(orgData);
        return {
          content: [{ 
            type: "text", 
            text: `Organization created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating organization: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the expected input parameters for the create_organization tool.
    schema: {
      name: z.string().describe("Organization name"),
      domain_names: z.array(z.string()).optional().describe("Domain names for the organization"),
      details: z.string().optional().describe("Details about the organization"),
      notes: z.string().optional().describe("Notes about the organization"),
      tags: z.array(z.string()).optional().describe("Tags for the organization")
    },
  • src/server.js:48-52 (registration)
    Registration of all tools, including create_organization from organizationsTools, to the MCP server using server.tool().
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • ZendeskClient helper method invoked by the tool handler to perform the actual API POST request for creating an organization.
    async createOrganization(data) {
      return this.request("POST", "/organizations.json", { organization: data });
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