Lara Translate MCP Server

list_memories

Read-onlyIdempotent

Retrieve all translation memories in your Lara Translate account to check available resources for translation projects.

Instructions

Lists all translation memories in your Lara Translate account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Translation memories accessible to the authenticated account

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.1.0Oct 15, 2026
- addedOutput schema / properties / items / items / properties / externalId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / externalId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / isPersonal / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / isPersonal / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / ownerId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / ownerId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / secret / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / secret / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
Changed19 schema fields changedv2.0.1Oct 13, 2026
- addedOutput schema / properties / items / items / properties / collaboratorsCount / anyOf
```
Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / collaboratorsCount / maximum
```
Removed value: -9007199254740991
```
- removedOutput schema / properties / items / items / properties / collaboratorsCount / minimum
```
Removed value: --9007199254740991
```
- removedOutput schema / properties / items / items / properties / collaboratorsCount / type
```
Removed value: -"integer"
```
- addedOutput schema / properties / items / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / createdAt / description
```
Removed value: -"ISO 8601 timestamp"
```
- removedOutput schema / properties / items / items / properties / createdAt / type
```
Removed value: -"string"
```
- changedOutput schema / properties / items / items / properties / externalId / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / items / items / 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 / items / items / properties / isPersonal / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / ownerId / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / secret / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / items / items / properties / sharedAt / anyOf
```
Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / sharedAt / description
```
Removed value: -"ISO 8601 timestamp"
```
- removedOutput schema / properties / items / items / properties / sharedAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / items / items / properties / updatedAt / anyOf
```
Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / updatedAt / description
```
Removed value: -"ISO 8601 timestamp"
```
- removedOutput schema / properties / items / items / properties / updatedAt / type
```
Removed value: -"string"
```
- changedOutput schema / properties / items / items / required
```
Previous value: -[
-  "id",
-  "createdAt",
-  "updatedAt",
-  "sharedAt",
-  "name",
-  "ownerId",
-  "collaboratorsCount",
-  "isPersonal"
-]New value: +[
+  "id",
+  "name"
+]
```
Changed1 schema field changedv2.0.0Sep 29, 2026
- removedOutput schema / properties / items / items / 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": false,
+  "properties": {
+    "items": {
+      "description": "Translation memories accessible to the authenticated account",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Addedv1.0.0Jan 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the account-wide scope ("all ... in your account"), with nothing about pagination, result size, or ordering. With annotations carrying the burden, this is minimally adequate.

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?

A single front-loaded sentence with no filler; every word (verb, resource, scope) earns its place. Nothing is buried or repeated.

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?

For a zero-parameter read-only list tool with an output schema present, the description does not need to explain return values or pagination details. Combined with annotations that cover safety and idempotency, it is nearly complete, lacking only explicit sibling routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline for a no-param tool is 4. The description correctly implies the call is unfiltered and account-scoped.

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?

The description gives a specific verb ("Lists") and resource ("translation memories") plus scope ("in your Lara Translate account"), so an agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like list_glossaries or get_glossary, so it falls short of a 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 mention of alternatives, and no indication of prerequisites or ordering relative to create_memory/update_memory. Usage is only weakly implied by the verb "Lists".

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