Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

delete_translation

Destructive

Delete a translation from your translation memory by specifying the memory ID, source and target languages, and the sentence with its translation.

Instructions

Deletes a translation from a translation memory in your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID or list of IDs where to delete the translation unit from. Format: mem_xyz123
sourceYesThe source language code of the sentence
targetYesThe target language code of the translation
sentenceYesThe source sentence
translationYesThe translated sentence
tuidNoTranslation Unit unique identifier
sentence_beforeNoThe sentence before the source sentence to specify the context of the translation unit
sentence_afterNoThe sentence after the source sentence to specify the context of the translation unit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesImport job identifier
beginNoBegin offset of the import
endNoEnd offset of the import
channelNoChannel identifier used by the import
sizeNoTotal number of units in the import
progressNoImport progress between 0 and 1 (1 means complete)
Behavior3/5

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

The description adds minimal behavioral context beyond the annotations. The annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of deletion adds little. It doesn't clarify irreversibility, permission requirements, or side effects, but the annotations carry the main burden.

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?

The description is a single concise sentence that conveys the core purpose without extraneous detail. It is front-loaded and efficient, with no wasted words.

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?

Given the tool has 8 parameters (5 required) and an output schema, the description is adequately complete. The schema covers parameter details, and annotations provide safety context. However, it could mention that deletion is permanent or affected data scope.

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 the input schema already describes all parameters thoroughly. The description adds no extra meaning to parameters beyond what the schema provides, meeting the baseline expectation.

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?

The description clearly states the action ('deletes a translation') and the resource ('translation memory in your Lara Translate account'), providing a specific verb and resource that distinguishes it from sibling tools like add_translation or list_memories.

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?

The description offers no guidance on when to use this tool vs alternatives, such as delete_memory or update_memory. It does not mention prerequisites, exclusions, or context for appropriate use, leaving the agent to infer usage from the name alone.

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/translated/lara-mcp'

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