Skip to main content
Glama

Remove Translations

remove_translations

Remove translation keys from all locale files in a specified layer. Preview changes with dry run before applying.

Instructions

Remove one or more translation keys from ALL locale files in the specified layer. Use dryRun to preview changes before applying them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerYesLayer name from discover (e.g., "root", "app-admin"). The key will be removed from ALL locale files in this layer.
keysYesDot-separated key paths to remove from every locale file in the layer. Example: ["common.actions.delete", "auth.errors.expired"].
dryRunNoWhen true, returns a preview of what would be removed without writing any files. Default: false.
projectDirNoAbsolute path to the Nuxt project root. Defaults to server cwd. Example: "/home/user/my-app".
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses destructive behavior (removes from ALL locale files) and provides dryRun for preview. Does not mention reversibility or error handling for missing keys.

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?

One concise sentence then schema. All essential information is present without redundancy.

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?

Covers key purpose, dryRun, and layer scope. Could mention behavior when keys don't exist, but schema descriptions for parameters are adequate.

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 coverage is 100%, so baseline is 3. Description restates parameter descriptions from schema without adding significant new meaning beyond the schema fields.

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?

Title and description clearly state verb 'remove' and resource 'translation keys from ALL locale files in specified layer'. Distinguishes from siblings like 'remove_orphan_keys' and 'rename_translation_key' by scope and action.

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?

Clearly states when to use: removing translation keys from all locale files in a layer, with dryRun for preview. Does not explicitly say when not to use or mention alternatives, though siblings exist for other removal scenarios.

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/fabkho/the-i18n-kit'

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