Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

update_organization

Modify Zendesk organization details including name, domain names, notes, and tags by providing the organization ID and updated values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrganization ID to update
nameNoUpdated organization name
domain_namesNoUpdated domain names
detailsNoUpdated details
notesNoUpdated notes
tagsNoUpdated tags

Implementation Reference

  • The MCP tool handler for 'update_organization'. Prepares the update data from optional parameters and delegates to zendeskClient.updateOrganization, returning formatted success or error response.
    handler: async ({ id, name, domain_names, details, notes, tags }) => {
      try {
        const orgData = {};
        
        if (name !== undefined) orgData.name = name;
        if (domain_names !== undefined) orgData.domain_names = domain_names;
        if (details !== undefined) orgData.details = details;
        if (notes !== undefined) orgData.notes = notes;
        if (tags !== undefined) orgData.tags = tags;
        
        const result = await zendeskClient.updateOrganization(id, orgData);
        return {
          content: [{ 
            type: "text", 
            text: `Organization updated successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error updating organization: ${error.message}` }],
          isError: true
        };
      }
  • Zod schema defining the input parameters for the update_organization tool, including required ID and optional fields.
    schema: {
      id: z.number().describe("Organization ID to update"),
      name: z.string().optional().describe("Updated organization name"),
      domain_names: z.array(z.string()).optional().describe("Updated domain names"),
      details: z.string().optional().describe("Updated details"),
      notes: z.string().optional().describe("Updated notes"),
      tags: z.array(z.string()).optional().describe("Updated tags")
    },
  • src/server.js:47-52 (registration)
    Registers all MCP tools, including 'update_organization', with the McpServer by iterating over the combined tools array.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • ZendeskClient method that performs the actual PUT request to the Zendesk Organizations API endpoint.
    async updateOrganization(id, data) {
      return this.request("PUT", `/organizations/${id}.json`, {
        organization: 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