Skip to main content
Glama

export_translations

Converts JSON or Flutter ARB translation catalogs into XLIFF 1.2/2.0 or TMX 1.4 exchange files for translation agencies and TMS platforms such as Crowdin, Lokalise, or Trados.

Instructions

Exports translation catalogs (JSON or Flutter ARB) into standard XLIFF (1.2 / 2.0) or TMX 1.4 exchange files for professional translation agencies and Translation Management Systems (Crowdin, Lokalise, Phrase, Smartling, Trados).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_translations"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExchange standard: 'xliff-1.2' (standard OASIS XLIFF), 'xliff-2.0' (modern XLIFF 2), or 'tmx-1.4' (LISA Translation Memory eXchange). Defaults to 'xliff-1.2'.xliff-1.2
namespacesNoOptional list of namespaces to limit export to.
outputPathNoFile or directory path to save exported exchange files. If omitted, returns output in content.
projectPathNoOptional project root directory. Defaults to current working directory.
includeNotesNoWhether to include translator notes / ARB descriptions. Defaults to true.
sourceLocaleNoSource language code (e.g. 'en'). Defaults to detected source locale.
targetLocalesNoTarget language codes to export (e.g. ['fr', 'de', 'es']).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It implies file creation from the outputPath parameter but never states whether files are overwritten, whether the operation is read-only or mutating, or what permissions/setup the project requires. The vendor list adds audience context but no behavioral contract.

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?

A single well-formed sentence with the purpose front-loaded before the format and platform details. The parenthetical list of five TMS vendors is somewhat marketing-flavored and only marginally earns its space, but the overall structure is tight.

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?

For a 7-parameter, all-optional tool with no output schema and no annotations, the definition covers what the tool produces but not how it behaves (file overwrite, error handling, prerequisites). It is adequate to call the tool, but leaves the agent guessing about side effects.

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 every parameter including the format enum and its defaults is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb (Exports), a specific resource (translation catalogs in JSON or Flutter ARB), and the exact output artifacts (XLIFF 1.2/2.0, TMX 1.4). It is clearly distinct from import_translations by direction, though no sibling is named explicitly.

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 only implied through the stated audience: professional translation agencies and TMS platforms such as Crowdin or Lokalise. There is no explicit when-to-use versus when-not, and no guidance on choosing between export and other catalog-producing siblings like format_catalogs or generate_pseudolocale.

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