Skip to main content
Glama

import_keys

Add translation keys with multiple language values to a Tolgee project using a list of key objects.

Instructions

Import localization keys with translations into a Tolgee project.

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

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

Example keys format:
    [{"name": "greeting", "translations": {"en": "Hello", "fr": "Bonjour"}}]

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?

With no annotations provided, the description carries full burden but omits critical behavioral details. It does not disclose handling of duplicate keys (overwrite vs. error), whether partial failures are possible, required permissions, or idempotency. This is a significant gap for a mutation tool.

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 description is well-organized with clear sections (Args, Example) and an example that aids understanding. It is appropriately sized for the tool's complexity, though the example could be condensed.

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?

Given moderate complexity, no annotations, and a schema with 0% description coverage, the description adequately covers parameter semantics and provides an example. However, it lacks completeness in behavioral aspects (error handling, output format, permissions) and does not leverage the existing output schema to explain return values.

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 description coverage is 0%, so the description compensates well. It explains that 'project_id' is numeric and 'keys' is a list of objects with 'name' and 'translations' fields, adding meaning beyond the minimal schema. However, it could further clarify the 'translations' dictionary structure (e.g., expected language tags).

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 clearly states the tool imports localization keys with translations into a Tolgee project. However, it does not differentiate from the sibling tool 'import_translations', which may have similar behavior, reducing clarity slightly.

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 explicit guidance on when to use this tool versus alternatives like 'create_key' (single key creation) or 'import_translations'. The description assumes bulk import but doesn't state this or provide criteria for choosing among siblings.

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