Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_macro

Create automated macros in Zendesk Support to streamline ticket management by defining reusable actions for common customer service workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesMacro title
descriptionNoMacro description
actionsYesActions to perform when macro is applied

Implementation Reference

  • The primary handler function for the 'create_macro' MCP tool. Validates inputs via schema, constructs macro data, calls the Zendesk client to create the macro, and returns formatted success or error response.
    handler: async ({ title, description, actions }) => {
      try {
        const macroData = {
          title,
          description,
          actions
        };
        
        const result = await zendeskClient.createMacro(macroData);
        return {
          content: [{ 
            type: "text", 
            text: `Macro created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating macro: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'create_macro' tool defining required title, optional description, and actions array.
    schema: {
      title: z.string().describe("Macro title"),
      description: z.string().optional().describe("Macro description"),
      actions: z.array(z.object({
        field: z.string().describe("Field to modify"),
        value: z.any().describe("Value to set")
      })).describe("Actions to perform when macro is applied")
    },
  • The complete tool definition object for 'create_macro' within the exported macrosTools array, which is later imported and registered in server.js.
    {
      name: "create_macro",
      description: "Create a new macro",
      schema: {
        title: z.string().describe("Macro title"),
        description: z.string().optional().describe("Macro description"),
        actions: z.array(z.object({
          field: z.string().describe("Field to modify"),
          value: z.any().describe("Value to set")
        })).describe("Actions to perform when macro is applied")
      },
      handler: async ({ title, description, actions }) => {
        try {
          const macroData = {
            title,
            description,
            actions
          };
          
          const result = await zendeskClient.createMacro(macroData);
          return {
            content: [{ 
              type: "text", 
              text: `Macro created successfully!\n\n${JSON.stringify(result, null, 2)}`
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating macro: ${error.message}` }],
            isError: true
          };
        }
      }
  • Supporting method in ZendeskClient class that sends POST request to Zendesk API /macros.json endpoint to create the macro.
    async createMacro(data) {
      return this.request("POST", "/macros.json", { macro: data });
    }
  • src/server.js:48-52 (registration)
    The registration loop in the main server file that dynamically registers all tools from various modules, including the 'create_macro' tool from macrosTools.
    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