Skip to main content
Glama

import_translations

Quickly add translations to a Tolgee project by supplying key names and language-value pairs.

Instructions

Import translations into a Tolgee project using single-step import.

Each key object should have a "name" and "translations" mapping language tags to values.

Args:
    project_id: The numeric ID of the project.
    keys: List of key objects with "name" (str) and "translations" (dict of language_tag -> value).

Example:
    [{"name": "hello", "translations": {"en": "Hello", "de": "Hallo"}}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
keysYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Lacks disclosure of side effects like overwriting existing translations, idempotency, or error handling. Annotations absent, so description should provide more behavioral context.

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?

Concise with three sentences plus Args and example. The example is helpful, but the structure could be more formal. Yet no unnecessary content.

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?

Covers parameters adequately but misses return value description and usage context. With output schema present, return details could be omitted, but still lacks error handling and conflict behavior.

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 has 0% description coverage, but description explains project_id as numeric and keys as list of objects with 'name' and 'translations' structure, adding value beyond the loose schema definition.

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 the tool imports translations into a Tolgee project using a single-step import, distinguishing it from siblings like import_keys or create_or_update_translations.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. With many sibling tools, this omission reduces clarity for an AI agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ytarfa/tolgee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server