Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr

Find Help Center Translation Gaps

find_translation_gaps
Read-onlyIdempotent

Audit Zendesk Help Center categories and sections for missing or draft translations in a target locale, so you can fix gaps before publishing.

Instructions

Audit the Help Center tree for a target locale and report every category and section that has no translation, or one that is still an unpublished draft. Use it before or after translating articles: an article published in a second locale is unreachable while its parent section only exists in the source locale. Listing sections in that locale cannot answer this — a node with no translation is simply absent, without saying why, and a node whose translation is an unpublished draft may still be listed under its draft name — so this audit reads the draft flag on each node instead of trusting that listing. Costs two listings and covers up to 100 categories and 100 sections; past that only the first page of each level is audited, and the report says so — pass category_id to narrow it. Fix what it reports with set_section_translation / set_category_translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeYesLocale to audit, e.g. "fr" or "de" — usually a non-default active locale of the Help Center (zendesk-hc://topology lists them). A locale that is not active is reported as a warning, since every node would then look untranslated.
category_idNoRestrict the audit to this category and the sections it contains (id from list_categories). Omit to sweep the whole tree, which costs two listings and covers up to 100 categories and 100 sections.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, the description discloses the tool's cost ('Costs two listings'), its hard limits (100 categories/sections, with truncation 'the report says so'), and its internal approach (reads the draft flag on each node). This is substantial and consistent with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, but the later motivational example about unreachable articles could be tightened. Still, every remaining sentence conveys necessary operational detail, so it is concise enough for a complex audit tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description thoroughly covers what, when, why, and operational limits, but with no output schema it stops short of specifying the report's exact structure (fields, how 'missing' vs 'draft' are marked). That missing detail is the main gap; otherwise it's highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the consequence of omitting category_id (whole-tree sweep with limits) and the importance of an active locale, which goes beyond the schema's descriptions without over-explaining.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Audit the Help Center tree for a target locale' — a specific verb, resource, and outcome — and explicitly contrasts with sibling listing tools by explaining why 'listing sections in that locale cannot answer this.' This clearly distinguishes the tool from list_categories and list_sections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit timing ('Use it before or after translating articles'), explains why alternatives fail, and names follow-up tools ('Fix what it reports with set_section_translation / set_category_translation'). It also advises passing category_id to narrow scope when hitting the 100/100 limit.

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/fruggr/zendesk-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server