Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_view

Create custom ticket views in Zendesk by defining title, description, and filtering conditions to organize and prioritize support requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesView title
descriptionNoView description
conditionsYesConditions for the view

Implementation Reference

  • The handler function that executes the 'create_view' tool logic. It constructs the view data from inputs and calls the Zendesk client to create the view, returning formatted success or error content.
    handler: async ({ title, description, conditions }) => {
      try {
        const viewData = {
          title,
          description,
          conditions
        };
        
        const result = await zendeskClient.createView(viewData);
        return {
          content: [{ 
            type: "text", 
            text: `View created successfully!\n\n${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating view: ${error.message}` }],
          isError: true
        };
      }
    }
  • The Zod schema defining the input parameters for the 'create_view' tool: title (required string), description (optional string), conditions (object with all/any filter arrays).
    schema: {
      title: z.string().describe("View title"),
      description: z.string().optional().describe("View description"),
      conditions: z.object({
        all: z.array(z.object({
          field: z.string().describe("Field to filter on"),
          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 filter on"),
          operator: z.string().describe("Operator for comparison"),
          value: z.any().describe("Value to compare against")
        })).optional()
      }).describe("Conditions for the view")
    },
  • src/server.js:48-52 (registration)
    The registration code in the MCP server that dynamically registers the 'create_view' tool (included in viewsTools) 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,
      });
    });
  • Helper method in ZendeskClient that makes the POST API request to /views.json to create a new view using the provided data.
    async createView(data) {
      return this.request("POST", "/views.json", { view: data });
    }
  • src/server.js:37-37 (registration)
    Inclusion of viewsTools (containing create_view) into the allTools array for registration.
    ...viewsTools,
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