Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Update translation

update-translation-tool
Destructive

Save a complete translation of a form into one language. Pass translated_content mirroring the structure of source_messages from get-translation-tool, with every string translated. If the language has not been added to the form yet it is added automatically (requires a Pro plan, max 20 languages per form). Translations go live immediately for the published form. Non-editable system messages are set automatically and any value you pass for them is ignored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_slug": "<form_slug>",
      "language": "<language>",
      "translated_content": "<translated_content>"
    },
    "name": "update-translation-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesLanguage code to save the translation for, e.g. "de", "fr", "zh-cn", "pt-br".
form_slugYesThe form's slug.
translated_contentYesThe complete translated messages: same structure as source_messages from get-translation-tool (system_messages + field_messages), with every string translated into the target language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations: it discloses that translations go live immediately on published forms, that auto-adding a language requires a Pro plan with a 20-language cap, and that system-message values passed in are silently ignored. That last point is behavior an agent could not infer from structured data and would otherwise get wrong.

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?

Four sentences, all load-bearing, with the core action stated first and constraints layered after. Slightly dense but no filler or repetition.

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?

For a 3-param nested mutation tool with annotations and no output schema, the description covers payload construction, side effects, plan limits, and ignored fields. It does not say what the call returns on success or what happens when the 20-language cap is exceeded, which are the remaining gaps.

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 3-parameter baseline is 3; the description adds real meaning by tying translated_content's shape to source_messages from get-translation-tool, insisting every string be translated, and flagging that system-message entries are ignored. It does not add format detail for language codes, but the schema already covers that with examples.

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 and resource ('Save a complete translation of a form into one language') and implicitly distinguishes itself from get-translation-tool by naming it as the source of the expected structure. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete usage context: the payload must mirror source_messages from get-translation-tool with every string translated, and it explains that missing languages are auto-added. It lacks an explicit 'do not use this when...' or a named alternative for partial updates, so it stops short of full routing guidance.

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

All Youform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources