Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_automation

Create automated workflows in Zendesk by defining conditions and actions to manage tickets and improve support processes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesAutomation title
descriptionNoAutomation description
conditionsYesConditions for the automation
actionsYesActions to perform when automation conditions are met

Implementation Reference

  • The main handler function for the 'create_automation' tool. It constructs the automation data from input parameters and delegates to zendeskClient.createAutomation(), handling success and error responses.
    handler: async ({ title, description, conditions, actions }) => {
      try {
        const automationData = {
          title,
          description,
          conditions,
          actions
        };
        
        const result = await zendeskClient.createAutomation(automationData);
        return {
          content: [{ 
            type: "text", 
            text: `Automation created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating automation: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema for input validation of the 'create_automation' tool, defining required title, optional description, complex conditions object, and actions array.
    schema: {
      title: z.string().describe("Automation title"),
      description: z.string().optional().describe("Automation description"),
      conditions: z.object({
        all: z.array(z.object({
          field: z.string().describe("Field to check"),
          operator: z.string().describe("Operator for comparison"),
          value: z.any().describe("Value to compare against")
        })).optional(),
        any: z.array(z.object({
          field: z.string().describe("Field to check"),
          operator: z.string().describe("Operator for comparison"),
          value: z.any().describe("Value to compare against")
        })).optional()
      }).describe("Conditions for the automation"),
      actions: z.array(z.object({
        field: z.string().describe("Field to modify"),
        value: z.any().describe("Value to set")
      })).describe("Actions to perform when automation conditions are met")
    },
  • The complete tool definition object for 'create_automation', including name, description, schema, and handler. This object is part of the exported automationsTools array, which is imported and registered in src/server.js.
    {
      name: "create_automation",
      description: "Create a new automation",
      schema: {
        title: z.string().describe("Automation title"),
        description: z.string().optional().describe("Automation description"),
        conditions: z.object({
          all: z.array(z.object({
            field: z.string().describe("Field to check"),
            operator: z.string().describe("Operator for comparison"),
            value: z.any().describe("Value to compare against")
          })).optional(),
          any: z.array(z.object({
            field: z.string().describe("Field to check"),
            operator: z.string().describe("Operator for comparison"),
            value: z.any().describe("Value to compare against")
          })).optional()
        }).describe("Conditions for the automation"),
        actions: z.array(z.object({
          field: z.string().describe("Field to modify"),
          value: z.any().describe("Value to set")
        })).describe("Actions to perform when automation conditions are met")
      },
      handler: async ({ title, description, conditions, actions }) => {
        try {
          const automationData = {
            title,
            description,
            conditions,
            actions
          };
          
          const result = await zendeskClient.createAutomation(automationData);
          return {
            content: [{ 
              type: "text", 
              text: `Automation created successfully!\n\n${JSON.stringify(result, null, 2)}`
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating automation: ${error.message}` }],
            isError: true
          };
        }
      }
  • ZendeskClient helper method invoked by the tool handler to perform the actual API POST request to create an automation.
    async createAutomation(data) {
      return this.request("POST", "/automations.json", { automation: data });
    }
  • src/server.js:48-52 (registration)
    The registration loop in the main server file that registers all tools, including 'create_automation' from automationsTools, by calling server.tool() for each.
    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