Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_trigger

Create automated triggers in Zendesk Support to perform actions when specific ticket conditions are met, streamlining ticket management workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTrigger title
descriptionNoTrigger description
conditionsYesConditions for the trigger
actionsYesActions to perform when trigger conditions are met

Implementation Reference

  • The handler function implementing the core logic for the 'create_trigger' MCP tool: constructs trigger data from inputs and invokes the Zendesk client to create the trigger, handling success and error responses.
    handler: async ({ title, description, conditions, actions }) => {
      try {
        const triggerData = {
          title,
          description,
          conditions,
          actions
        };
        
        const result = await zendeskClient.createTrigger(triggerData);
        return {
          content: [{ 
            type: "text", 
            text: `Trigger created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating trigger: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod input schema defining and validating the parameters for the 'create_trigger' tool: title (required), description (optional), conditions (all/any), and actions.
    schema: {
      title: z.string().describe("Trigger title"),
      description: z.string().optional().describe("Trigger 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 trigger"),
      actions: z.array(z.object({
        field: z.string().describe("Field to modify"),
        value: z.any().describe("Value to set")
      })).describe("Actions to perform when trigger conditions are met")
    },
  • src/server.js:48-52 (registration)
    Dynamic registration of the 'create_trigger' tool (included in triggersTools spread into allTools) by calling server.tool with its name, schema, handler, and description.
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Supporting ZendeskClient method that performs the underlying API call to POST /triggers.json for creating a trigger, used by the tool handler.
    async createTrigger(data) {
      return this.request("POST", "/triggers.json", { trigger: 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