Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

get_talk_stats

Retrieve analytics and performance metrics for Zendesk Talk phone support, including call volume, wait times, and agent activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_talk_stats'. Calls zendeskClient.getTalkStats(), stringifies the result as JSON text response, or returns error message.
    handler: async () => {
      try {
        const result = await zendeskClient.getTalkStats();
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error getting Talk stats: ${error.message}` }],
          isError: true
        };
      }
    }
  • src/server.js:48-52 (registration)
    Registration of all tools (including 'get_talk_stats') on the MCP server via server.tool() calls in a loop over allTools which includes talkTools.
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Helper method in ZendeskClient that performs the API request to fetch Talk statistics from the '/channels/voice/stats.json' endpoint.
    async getTalkStats() {
      return this.request("GET", "/channels/voice/stats.json");
    }
  • src/tools/talk.js:4-26 (registration)
    Tool specification definition: exports talkTools array with 'get_talk_stats' tool including name, description, empty schema, and reference to handler.
    export const talkTools = [
      {
        name: "get_talk_stats",
        description: "Get Zendesk Talk statistics",
        schema: {},
        handler: async () => {
          try {
            const result = await zendeskClient.getTalkStats();
            return {
              content: [{ 
                type: "text", 
                text: JSON.stringify(result, null, 2)
              }]
            };
          } catch (error) {
            return {
              content: [{ type: "text", text: `Error getting Talk stats: ${error.message}` }],
              isError: true
            };
          }
        }
      }
    ];

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

D1/5.0
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.