Lara Translate MCP Server

delete_glossary_entry

DestructiveIdempotent

Remove a term or GUID from your Lara Translate glossary. Specify term for monodirectional glossaries or guid for multidirectional ones.

Instructions

Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The glossary ID (format: gls_*, e.g., 'gls_xyz123')
`guid`	No	The entry GUID to delete. Use this for multidirectional glossaries.
`term`	No	The term to delete. Use this for monodirectional glossaries.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Import job identifier
`end`	No	End offset of the import
`size`	No	Total number of entries in the import
`begin`	No	Begin offset of the import
`channel`	No	Channel identifier used by the import
`progress`	No	Import progress between 0 and 1 (1 means complete)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Sep 29, 2026
- removedOutput schema / additionalProperties
```
Removed value: -{}
```

Changed1 schema field changedv1.0.4May 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "begin": {
+      "description": "Begin offset of the import",
+      "type": "number"
+    },
+    "channel": {
+      "description": "Channel identifier used by the import",
+      "type": "number"
+    },
+    "end": {
+      "description": "End offset of the import",
+      "type": "number"
+    },
+    "id": {
+      "description": "Import job identifier",
+      "type": "string"
+    },
+    "progress": {
+      "description": "Import progress between 0 and 1 (1 means complete)",
+      "type": "number"
+    },
+    "size": {
+      "description": "Total number of entries in the import",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — it never states the deletion is permanent, whether the entry can be recovered, or what happens on a missing id.

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 short sentences, purpose front-loaded and the parameter routing second. No filler or 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?

With annotations covering destructiveness/idempotency, an output schema covering returns, and a fully documented schema, the definition is nearly self-sufficient. It only omits any note on irreversibility or error behavior for the destructive path.

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% and the schema itself already labels guid for multidirectional and term for monodirectional glossaries, so the description largely restates structured data. It adds no format, validation, or mutual-exclusivity detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Deletes an entry from a glossary.' The noun 'entry' distinguishes it from the sibling delete_glossary, but no sibling is named explicitly and the account scope is the only additional qualifier.

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?

Gives explicit conditional routing: use term for monodirectional glossaries, guid for multidirectional glossaries. That is clear when-to-use-which guidance, but it does not address when to prefer this tool over alternatives or any preconditions.

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