Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

update_macro

Modify existing Zendesk macros by updating their title, description, or actions to streamline customer support workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMacro ID to update
titleNoUpdated macro title
descriptionNoUpdated macro description
actionsNoUpdated actions

Implementation Reference

  • The handler function that implements the core logic of the 'update_macro' tool, constructing macro data and calling the Zendesk client to update the macro.
    handler: async ({ id, title, description, actions }) => {
      try {
        const macroData = {};
        
        if (title !== undefined) macroData.title = title;
        if (description !== undefined) macroData.description = description;
        if (actions !== undefined) macroData.actions = actions;
        
        const result = await zendeskClient.updateMacro(id, macroData);
        return {
          content: [{ 
            type: "text", 
            text: `Macro updated successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error updating macro: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the 'update_macro' tool.
    schema: {
      id: z.number().describe("Macro ID to update"),
      title: z.string().optional().describe("Updated macro title"),
      description: z.string().optional().describe("Updated macro description"),
      actions: z.array(z.object({
        field: z.string().describe("Field to modify"),
        value: z.any().describe("Value to set")
      })).optional().describe("Updated actions")
    },
  • src/server.js:47-52 (registration)
    Generic registration loop that registers the 'update_macro' tool (included via macrosTools in allTools) with the MCP server.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Helper method in ZendeskClient that performs the API request to update a macro.
    async updateMacro(id, data) {
      return this.request("PUT", `/macros/${id}.json`, { macro: 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