Skip to main content
Glama
fruggr

Zendesk MCP Server by Fruggr

by fruggr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Article Translation

create_article_translation

Create a translation for an existing Zendesk article in a new locale by supplying the translated title and full HTML body.

Instructions

Create a translation for an existing article in a specific locale. The article must already exist (create it with create_article); this adds a new localized version and returns the created translation (locale, title, draft state). The target locale must not already have a translation — use update_article_translation to modify an existing one, and list_article_translations to see which locales exist. Provide the full HTML body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTranslated body (HTML)
draftNoCreate the translation as a draft (not visible to end users). Defaults to false (published).
titleYesTranslated article title.
localeYesTarget locale (e.g., "fr", "de")
article_idYesID of the existing article to translate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.3.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed3 schema fields changedv2.2.0
    • addedInput schema / properties / article_id / description
      Added value: +"ID of the existing article to translate."
    • addedInput schema / properties / draft / description
      Added value: +"Create the translation as a draft (not visible to end users). Defaults to false (published)."
    • addedInput schema / properties / title / description
      Added value: +"Translated article title."
  4. First observedv1.7.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not idempotent, not destructive, open-world). The description adds meaningful context beyond them: the article-existence prerequisite, the no-existing-translation constraint (which effectively explains the non-idempotent behavior), and the return payload (locale, title, draft state). It does not mention permission/auth requirements, which is the remaining gap.

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

Conciseness5/5

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

Front-loads the core action, then the prerequisites, the constraint with alternatives, and the input requirement. Every sentence carries distinct information with no repetition.

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?

For a mutation tool with no output schema, the description covers the action, prerequisites, constraint, alternatives, required inputs, and even the shape of the returned translation. Nothing an agent needs to invoke it correctly is missing.

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%, so all five parameters are already documented in the schema. The description only reinforces the body requirement ('full HTML body') and the locale/draft concepts, adding marginal meaning over the structured fields. Baseline 3 is appropriate.

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?

States a specific verb (create) and resource (article translation) scoped to a locale, and explicitly distinguishes itself from create_article (which creates the source article) and update_article_translation (which modifies an existing translation). An agent can route correctly without opening any schema.

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?

Explicitly states the precondition (article must already exist, use create_article first), the constraint (target locale must not already have a translation), and names the two alternatives — update_article_translation for modifying and list_article_translations for discovering existing locales. Nothing is left to inference.

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