Multilocale Translations

Delete a string in every language

delete_phrase

Destructive

Use this when someone asks to remove a key from their translations. Returns how many language rows were deleted and which other projects shared them; a shared string is deleted permanently for those projects too. Not for removing only one language's translation.

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": {
      "project": "<project>",
      "key": "<key>"
    },
    "name": "delete_phrase"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes	Exact key to delete in every language
`project`	Yes	Project id or name that has the key

Output Schema

Name	Required	Description
`key`	Yes
`status`	Yes
`project`	Yes
`sharedProjects`	Yes	Other projects the deleted string was also removed from
`deletedTranslationCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 28, 2026

changedInput schema / properties / key / description

Previous value: -"Exact key whose complete locale group should be deleted"New value: +"Exact key to delete in every language"

changedInput schema / properties / project / description

Previous value: -"Project id or name that contains the key to delete"New value: +"Project id or name that has the key"

addedOutput schema / properties / sharedProjects / description

Added value: +"Other projects the deleted string was also removed from"

First observedAug 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so safety is covered. The description adds genuinely new context beyond them: the cross-project blast radius ('a shared string is deleted permanently for those projects too') and the deletion count returned. It does not explain the non-idempotent behavior, which the annotations flag.

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 tight sentences with the usage trigger front-loaded, then the side-effect warning, then the exclusion. Every sentence carries information and none is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present (return values needn't be described) and annotations covering the safety profile, the description supplies the remaining critical piece an agent needs: the permanent, multi-project consequence of deleting a shared string. Nothing essential is missing.

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 both parameters (key, project) are fully documented in the schema. The description reinforces that the key is deleted 'in every language' but adds no syntax, format, or lookup guidance beyond what is already there. Baseline 3 is 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 (delete/remove) and resource (a key/string in translations) with the critical scope qualifier 'in every language', which distinguishes it from the many sibling phrase tools like update_phrase or add_phrase. An agent can identify the operation without opening the schema.

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?

'Use this when someone asks to remove a key from their translations' gives clear positive context, and 'Not for removing only one language's translation' gives an explicit exclusion. It stops short of naming the sibling tool that handles single-language removal, but the boundary is unambiguous.

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

All Multilocale Translations tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?