Skip to main content
Glama

edit_translation

Add survey languages and edit translations: the default language, how respondents get a language, the language picker, per-language question/answer/block text and visibility, translator-scoped edits, and machine translation with a saved AI credential. delete_translation_language removes a language.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "edit_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesSurvey UUID
add_languageNoAdd a survey language (code like "es" or "pt-BR", and its display name).
auto_translateNoMachine-translate the survey into an added language with a saved AI credential (fill empty fields, or overwrite all). Calls the credential's provider.
set_language_pickerNoThe respondent-facing language picker question: type, title, options, and behavior.
set_default_languageNoMake an added language the survey's default (source) language.
set_language_routingNoHow respondents get a language: manual (the language picker) or system_language (their browser's).
set_translator_fieldNoTranslator-scoped edit of one translatable field.
add_translator_optionNoTranslator-scoped added answer option for one language.
set_block_translationNoOne language's text for a block's end-of-survey message or redirect.
set_answer_translationNoOne language's text for a question's answer fields (keys from read_translation include translatable_fields).
set_question_translationNoOne language's question title and media.
set_translator_visibilityNoTranslator-scoped show/hide of a question or option.
set_language_option_visibilityNoShow or hide an answer option for one language.
set_language_picker_translationNoOne language's text for the language picker itself.
set_language_question_visibilityNoShow or hide a question for one language.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare write access, non-idempotency, open-world behavior, and non-destructiveness. The description adds useful context that machine translation uses a saved AI credential and that translator-scoped edits exist, but it does not disclose side effects such as provider calls, overwrite consequences, or required confirmations beyond what the schema itself provides.

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 definition is front-loaded with the core verb and resource and uses a compact, dense list to cover a broad tool. It is appropriately sized for a 15-parameter multi-operation tool, though the single long sentence is less scannable than a structured list would be.

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

Completeness3/5

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

The description gives a useful high-level map of the tool's capabilities, and an output schema exists so return values need not be explained. However, for a tool with 15 optional nested operations, it omits the operational model: that these parameters represent alternative edits, whether multiple can be combined, and how they relate to survey_id.

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 the schema already documents all 15 operation parameters in detail. The description groups those parameters into meaningful areas (picker, default language, translator edits, machine translation), which adds some navigational value, but it does not add parameter-level syntax or selection rules beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource ('Add survey languages and edit translations') and enumerates the covered areas: default language, language acquisition, picker, per-language question/answer/block text, visibility, translator-scoped edits, and machine translation. It also distinguishes itself from delete_translation_language, though it does not explicitly contrast with read_translation or edit_question.

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

Usage Guidelines3/5

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

Usage is implied by the enumerated capabilities: adding a language or changing translation-related settings. The only alternative named is delete_translation_language, and there is no explicit guidance on when to use this instead of read_translation, edit_question, or edit_survey, nor any when-not conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources