Lara Translate MCP Server

delete_glossary

DestructiveIdempotent

Remove a glossary from your Lara Translate account by providing its glossary ID, clearing saved terminology you no longer need.

Instructions

Deletes a glossary from your Lara Translate account.

Input Schema

Name	Required	Description	Default
`id`	Yes	The glossary ID to delete (format: gls_*, e.g., 'gls_xyz123')

Output Schema

Name	Required	Description
`id`	Yes	Unique glossary identifier (format: gls_*)
`name`	Yes	Display name of the glossary
`ownerId`	No	Identifier of the glossary owner
`createdAt`	No
`updatedAt`	No
`isPersonal`	No	True if the glossary is private to the owner. Omitted for some account types (e.g. team plans).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.0Oct 15, 2026

addedOutput schema / properties / isPersonal / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / isPersonal / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```

addedOutput schema / properties / ownerId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / ownerId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed10 schema fields changedv2.0.1Oct 13, 2026

addedOutput schema / properties / createdAt / anyOf

Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / createdAt / description
```
Removed value: -"ISO 8601 timestamp"
```
removedOutput schema / properties / createdAt / type
```
Removed value: -"string"
```

changedOutput schema / properties / isPersonal / description

Previous value: -"True if the glossary is private to the owner"New value: +"True if the glossary is private to the owner. Omitted for some account types (e.g. team plans)."

changedOutput schema / properties / isPersonal / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

changedOutput schema / properties / ownerId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / updatedAt / anyOf

Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / updatedAt / description
```
Removed value: -"ISO 8601 timestamp"
```
removedOutput schema / properties / updatedAt / type
```
Removed value: -"string"
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "ownerId",
-  "createdAt",
-  "updatedAt",
-  "isPersonal"
-]New value: +[
+  "id",
+  "name"
+]

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": {
+    "createdAt": {
+      "description": "ISO 8601 timestamp",
+      "type": "string"
+    },
+    "id": {
+      "description": "Unique glossary identifier (format: gls_*)",
+      "type": "string"
+    },
+    "isPersonal": {
+      "description": "True if the glossary is private to the owner",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Display name of the glossary",
+      "type": "string"
+    },
+    "ownerId": {
+      "description": "Identifier of the glossary owner",
+      "type": "string"
+    },
+    "updatedAt": {
+      "description": "ISO 8601 timestamp",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "ownerId",
+    "createdAt",
+    "updatedAt",
+    "isPersonal"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

C2.9/5.0

Behavior2/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 structurally. The description adds no behavioral context of its own — no mention of irreversibility, effect on contained entries, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One clean, front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is partly the result of omitting useful detail rather than tight writing.

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

Completeness3/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 not be explained, and annotations carry the destructive/idempotent profile. Still missing are the operational preconditions of a deletion and any warning about consequences for related entries, which an agent would want before invoking a destructive call.

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%, and the id parameter's format (gls_* pattern) is fully documented in the schema. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 (Deletes) and resource (a glossary) with scope limited to the account. It does not distinguish itself from closely named siblings like delete_glossary_entry or delete_translation, leaving the agent to rely on the name alone.

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?

No when-to-use, when-not-to-use, or alternative routing is provided. Nothing tells the agent how this differs from delete_glossary_entry, nor whether preconditions (e.g., glossary must be empty, ownership) exist before calling.

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