Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_group

Create new support groups in Zendesk to organize agents and manage ticket routing. Specify group name and optional description for team organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGroup name
descriptionNoGroup description

Implementation Reference

  • The MCP tool handler function for 'create_group'. It constructs group data from inputs and delegates to zendeskClient.createGroup, returning a formatted success message or error.
    handler: async ({ name, description }) => {
      try {
        const groupData = {
          name,
          description
        };
        
        const result = await zendeskClient.createGroup(groupData);
        return {
          content: [{ 
            type: "text", 
            text: `Group created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating group: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the create_group tool: required 'name' and optional 'description'.
    schema: {
      name: z.string().describe("Group name"),
      description: z.string().optional().describe("Group description")
    },
  • src/server.js:48-52 (registration)
    Registration loop that adds the 'create_group' tool (included in groupsTools) to the MCP server using server.tool.
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Helper method in ZendeskClient that makes the API POST request to /groups.json to create a new group.
    async createGroup(data) {
      return this.request("POST", "/groups.json", { group: 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