Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Section Translations

list_section_translations
Read-onlyIdempotent

Lists per-locale name, description presence, and draft status for a help center section, identifying why it appears missing or with wrong text in a locale.

Instructions

List the translations of a Help Center section: for each locale, the localized name, whether a description is set, and whether the translation is published or still a draft. Reach for this when a section looks wrong in a locale, because list_sections with that locale cannot settle it: a section with no translation is omitted from it, while a section whose translation is an unpublished draft may still be listed there under the draft name — so appearing in that listing does not mean published, and the draft flag here is what decides. Fix either case with set_section_translation; to sweep every category and section at once, use find_translation_gaps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
section_idYesSection ID — the numeric id of the Help Center section. Obtain it from list_sections or the zendesk-hc://topology resource.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.17.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds crucial behavioral context: it returns per-locale flags for description and published status, and clarifies the subtle draft-vs-missing distinction that list_sections cannot reveal. No contradictions 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 first sentence is concise and front-loaded. The second sentence is long but packed with necessary edge-case reasoning and alternative tool guidance. No filler, but the density could be slightly trimmed without losing value.

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

Completeness5/5

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

Given no output schema, the description fully covers what the tool returns (for each locale: name, description-set flag, published/draft) and how to interpret it. It also covers edge cases and corrective actions, making it contextually complete for a list operation.

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

Parameters3/5

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

Schema description coverage is 100%; the only parameter (section_id) is fully documented with its type, source, and how to obtain it. The description adds no additional parameter semantics, which matches the baseline of 3 for high schema coverage.

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 clearly states that the tool lists translations of a Help Center section with details per locale (localized name, description set?, published/draft). It also distinguishes itself from list_sections and other related translation tools, making its purpose unambiguous.

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 explicitly says when to use the tool ('when a section looks wrong in a locale'), explains why the alternative list_sections is insufficient, and points to set_section_translation and find_translation_gaps for related actions. This is exemplary usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools