Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

delete_memory

DestructiveIdempotent

Deletes a translation memory from your Lara Translate account by ID, removing saved segments from future use.

Instructions

Deletes a translation memory from your Lara Translate account.

Input Schema

NameRequiredDescriptionDefault
idYesThe unique identifier of the memory to update. Format: mem_xyz123

Output Schema

NameRequiredDescriptionDefault
idYesUnique memory identifier (format: mem_*)
nameYesDisplay name of the memory
secretNoMemory secret, if any
ownerIdNoIdentifier of the memory owner
sharedAtNo
createdAtNo
updatedAtNo
externalIdNoExternal identifier (e.g. MyMemory ID) when imported
isPersonalNoTrue if the memory is private to the owner. Omitted for some account types (e.g. team plans).
collaboratorsCountNoNumber of collaborators with access to the memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.1.0
    • addedOutput schema / properties / externalId / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / externalId / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • 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"
      -]
    • addedOutput schema / properties / secret / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / secret / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  2. Changed19 schema fields changedv2.0.1
    • addedOutput schema / properties / collaboratorsCount / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / collaboratorsCount / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / collaboratorsCount / minimum
      Removed value: --9007199254740991
    • removedOutput schema / properties / collaboratorsCount / type
      Removed value: -"integer"
    • 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 / externalId / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / isPersonal / description
      Previous value: -"True if the memory is private to the owner"New value: +"True if the memory 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"
      +]
    • changedOutput schema / properties / secret / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / sharedAt / anyOf
      Added value: +[
      +  {
      +    "description": "ISO 8601 timestamp",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / sharedAt / description
      Removed value: -"ISO 8601 timestamp"
    • removedOutput schema / properties / sharedAt / type
      Removed value: -"string"
    • 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",
      -  "createdAt",
      -  "updatedAt",
      -  "sharedAt",
      -  "name",
      -  "ownerId",
      -  "collaboratorsCount",
      -  "isPersonal"
      -]New value: +[
      +  "id",
      +  "name"
      +]
  3. Changed1 schema field changedv2.0.0
    • removedOutput schema / additionalProperties
      Removed value: -{}
  4. Changed1 schema field changedv1.0.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "collaboratorsCount": {
      +      "description": "Number of collaborators with access to the memory",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "createdAt": {
      +      "description": "ISO 8601 timestamp",
      +      "type": "string"
      +    },
      +    "externalId": {
      +      "description": "External identifier (e.g. MyMemory ID) when imported",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "Unique memory identifier (format: mem_*)",
      +      "type": "string"
      +    },
      +    "isPersonal": {
      +      "description": "True if the memory is private to the owner",
      +      "type": "boolean"
      +    },
      +    "name": {
      +      "description": "Display name of the memory",
      +      "type": "string"
      +    },
      +    "ownerId": {
      +      "description": "Identifier of the memory owner",
      +      "type": "string"
      +    },
      +    "secret": {
      +      "description": "Memory secret, if any",
      +      "type": "string"
      +    },
      +    "sharedAt": {
      +      "description": "ISO 8601 timestamp",
      +      "type": "string"
      +    },
      +    "updatedAt": {
      +      "description": "ISO 8601 timestamp",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "createdAt",
      +    "updatedAt",
      +    "sharedAt",
      +    "name",
      +    "ownerId",
      +    "collaboratorsCount",
      +    "isPersonal"
      +  ],
      +  "type": "object"
      +}
  5. Addedv1.0.0

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 and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no note on irreversibility, permissions required, or what a repeat call returns despite idempotency.

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?

A single front-loaded sentence with no wasted words; the verb and resource come first. It is efficient, though it errs toward under-specification rather than over-explanation.

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?

With annotations covering destructiveness and an output schema handling the return contract, the description need not explain responses. However, for a destructive mutation it omits any caution about permanent deletion or re-run behavior, leaving it only minimally complete.

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 id parameter is documented in the schema and the baseline is 3. The description adds no extra meaning about the id format or source. Note the schema's param text says 'memory to update', a misleading carry-over, but that is a schema defect rather than a description one.

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 ('translation memory'), so an agent distinguishes it cleanly from list/create/update_memory. It stops short of explicitly naming sibling delete tools or how this differs operationally from them, so it earns 4 rather than 5.

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?

There is no when-to-use guidance, no preconditions, and no warning that this is an irreversible removal. The agent gets no help deciding whether to call this versus update_memory or another tool.

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