Lara Translate MCP Server

update_memory

DestructiveIdempotent

Update the name of a translation memory in your Lara Translate account by entering its ID and the new name.

Instructions

Updates a translation memory in your Lara Translate account.

Input Schema

Name	Required	Description	Default
`id`	Yes	The unique identifier of the memory to update. Format: mem_xyz123
`name`	Yes	The new name for the memory

Output Schema

Name	Required	Description
`id`	Yes	Unique memory identifier (format: mem_*)
`name`	Yes	Display name of the memory
`secret`	No	Memory secret, if any
`ownerId`	No	Identifier of the memory owner
`sharedAt`	No
`createdAt`	No
`updatedAt`	No
`externalId`	No	External identifier (e.g. MyMemory ID) when imported
`isPersonal`	No	True if the memory is private to the owner. Omitted for some account types (e.g. team plans).
`collaboratorsCount`	No	Number of collaborators with access to the memory

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.1.0Oct 15, 2026

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"
-]
```

Changed19 schema fields changedv2.0.1Oct 13, 2026

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"
+]

Changed2 schema fields changedv2.0.0Sep 29, 2026
- addedInput schema / properties / name / description
```
Added value: +"The new name for the memory"
```
- 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": {
+    "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"
+}

Addedv1.0.0Jan 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't clarify that only the name is mutable, whether the change is reversible, or what happens on invalid ids, leaving the behavioral burden entirely on structured fields.

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 efficient sentence with no waste, front-loading the verb and resource. It could have used the extra room to specify the rename scope, but it is not bloated.

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 the schema covers both parameters. What's missing is any statement that the update is limited to the name and any mutation caveats, which for a destructive-flagged write on a service object would be valuable.

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 both parameters (id, name) are documented, including the mem_xyz123 ID format. The description adds no syntax or semantic detail beyond the schema, so the baseline of 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 ('Updates') and resource ('translation memory') scoped to the Lara Translate account, which separates it from siblings like create_memory and delete_memory. However, it is vaguer than the annotation title 'Rename translation memory', which more precisely conveys that only the name is changed.

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 guidance, no prerequisites, and no mention of alternatives such as create_memory or delete_memory. The agent must infer from the schema that this tool is for renaming an existing memory.

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