the-i18n-mcp

by fabkho

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Remove Translations

remove_translations

DestructiveIdempotent

Delete specified translation keys from every locale file in a layer; preview with dry-run before applying.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`keys`	Yes	Dot-separated key paths to remove from every locale file in the layer. Example: ["common.actions.delete", "auth.errors.expired"].
`layer`	Yes	Layer name from discover (e.g., "root", "app-admin"). The keys are removed from ALL locale files in this layer.
`dryRun`	No	Return a preview of what would be removed without writing any files. Default: false.
`projectDir`	No	Absolute path to the project root. Defaults to I18N_PROJECT_DIR, then server cwd. Example: "/home/user/my-app".

Output Schema

TableJSON Schema

Name	Required	Description
`dryRun`	No	True when nothing was removed because a preview was asked for. Absent otherwise.
`message`	No	The step to take next, as the surface the call ran on phrases it. Present only when there is no summary to carry it.
`removed`	No	Dot-path keys removed from at least one locale file. Absent on a dry run.
`summary`	No	Counts of what the run did. Absent on a dry run.
`notFound`	No	Requested keys no locale file of the layer defined. Absent when every key existed.
`wouldRemove`	No	What a dry run would remove. Present only with dryRun.
`filesWritten`	No	Number of locale files changed on disk. Absent on a dry run.
`removedPerLocale`	No	One "locale:key" entry per file-level removal. Absent on a dry run.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.6Sep 12, 2026

changedInput schema / properties / dryRun / description

Previous value: -"When true, returns a preview of what would be removed without writing any files. Default: false."New value: +"Return a preview of what would be removed without writing any files. Default: false."

changedInput schema / properties / layer / description

Previous value: -"Layer name from discover (e.g., \"root\", \"app-admin\"). The key will be removed from ALL locale files in this layer."New value: +"Layer name from discover (e.g., \"root\", \"app-admin\"). The keys are removed from ALL locale files in this layer."

changedInput schema / properties / projectDir / description

Previous value: -"Absolute path to the Nuxt project root. Defaults to I18N_PROJECT_DIR, then server cwd. Example: \"/home/user/my-app\"."New value: +"Absolute path to the project root. Defaults to I18N_PROJECT_DIR, then server cwd. Example: \"/home/user/my-app\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "dryRun": {
+      "description": "True when nothing was removed because a preview was asked for. Absent otherwise.",
+      "type": "boolean"
+    },
+    "filesWritten": {
+      "description": "Number of locale files changed on disk. Absent on a dry run.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "message": {
+      "description": "The step to take next, as the surface the call ran on phrases it. Present only when there is no summary to carry it.",
+      "type": "string"
+    },
+    "notFound": {
+      "description": "Requested keys no locale file of the layer defined. Absent when every key existed.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "removed": {
+      "description": "Dot-path keys removed from at least one locale file. Absent on a dry run.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "removedPerLocale": {
+      "description": "One \"locale:key\" entry per file-level removal. Absent on a dry run.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "description": "Counts of what the run did. Absent on a dry run.",
+      "properties": {
+        "keysFound": {
+          "description": "Requested keys that existed and were removed.",
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "message": {
+          "description": "One sentence stating what the run did.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "keysFound",
+        "message"
+      ],
+      "type": "object"
+    },
+    "wouldRemove": {
+      "description": "What a dry run would remove. Present only with dryRun.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "key": {
+            "description": "Dot-path key that would be removed.",
+            "type": "string"
+          },
+          "locale": {
+            "description": "Locale the key would be removed from.",
+            "type": "string"
+          },
+          "oldValue": {
+            "description": "The value that would be lost."
+          }
+        },
+        "required": [
+          "locale",
+          "key",
+          "oldValue"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedv1.0.3Aug 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / projectDir / description

Previous value: -"Absolute path to the Nuxt project root. Defaults to server cwd. Example: \"/home/user/my-app\"."New value: +"Absolute path to the Nuxt project root. Defaults to I18N_PROJECT_DIR, then server cwd. Example: \"/home/user/my-app\"."

First observedv1.0.0Jun 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is handled. The description adds real value beyond that by disclosing the blast radius ('ALL locale files in the layer') and the dryRun preview path, which is exactly the context an agent needs before a destructive multi-file write.

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?

Two sentences, zero filler, and the destructive scope is front-loaded before the mitigation advice. Nothing is padded or restated.

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?

An output schema exists, so return values need no explanation, and annotations cover the mutation semantics. The description covers scope and previewing, but omits whether removal is recoverable or what happens to keys absent from some locale files—minor gaps for a destructive write tool.

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 all four parameters (keys, layer, dryRun, projectDir) are already fully documented in the schema. The description repeats the dryRun purpose but adds no format or syntax detail beyond what the schema provides, making the baseline 3 appropriate.

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 (remove translation keys) plus the exact scope (ALL locale files in the given layer). That scope statement cleanly separates it from siblings like move_translation_key and write_translations without the agent needing to open schemas.

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?

It gives one actionable usage instruction—use dryRun to preview before applying—which is genuinely helpful for a destructive tool. But it never says when to prefer this over alternatives such as move_translation_key, nor does it state prerequisites or when removal is inappropriate.

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

Deploy Server