Skip to main content
Glama

Create keys

create_keys

Create translation keys in a Tolgee project with optional translations and tags. Keys that already exist are silently skipped — their translations and tags are not updated. Use update_key and set_translation to modify existing keys.

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": {
      "keys": "<keys>"
    },
    "name": "create_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesList of keys to create
branchNoOptional: branch name
namespaceNoOptional: default namespace for all keys (individual keys can override)
projectIdNoID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"ID of the project (required for PAT, auto-resolved for PAK)"New value: +"ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, closed-world write. The description adds genuinely non-obvious behavior beyond that: existing keys are silently skipped and their translations/tags are NOT updated — a critical idempotency detail an agent would otherwise assume wrongly. It does not disclose partial-failure behavior or what a successful response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero filler, front-loaded with the core action and ending with the alternative routing. The skip-semantics sentence sits in the middle exactly where a caller would need it.

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 batch-create tool with a nested key array, full schema coverage, and no output schema, the description covers the essential risk (silent skipping). It stops short of saying whether the call is atomic, what is returned per key, or whether large batches are throttled.

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 (keys, branch, namespace, projectId, and the nested key fields) is already documented inline, including the namespace-override relationship. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 plus scope: 'Create translation keys in a Tolgee project with optional translations and tags.' The second and third sentences distinguish it from update_key and set_translation, so an agent can separate creation from modification without inspecting sibling schemas.

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?

Explicitly routes existing-key modification to update_key and set_translation and warns that existing keys are silently skipped rather than updated. It lacks explicit exclusions such as batch-size limits, branch prerequisites, or when to prefer list_keys/search_keys to check for existence first.

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.