get_v1_translate_memory
List returns the org's own translation-memory entries, newest first, optionally narrowed to one target language and/or one position on the review ladder.
List returns the org's own translation-memory entries, newest first, optionally narrowed to one target language and/or one position on the review ladder. It is the review lane's read: what a human reviewer works through.
The org is ALWAYS the validated principal's org, never a request field, so one tenant can never read another's memory — the entries hold customer source text.
| Tool | get_v1_translate_memory |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | GET /v1/translate/memory |
| Product | translate |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
limit | integer | — | — | — | Limit caps the rows returned. Non-positive or unparseable means the server default (200); the ceiling is 1000. |
state | string | — | — | — | State narrows to one position on the review ladder: machine, suggested, approved or published. |
target | string | — | — | — | Target narrows to one target language tag (BCP-47, e.g. "es" or "pt-BR"). |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_translate_memory",
"arguments": {
"limit": 0,
"state": "<state>",
"target": "<target>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. limit holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_translate_memory | GET /v1/translate/memory | translate | List returns the org's own translation-memory entries, newest first, optionally narrowed… |
The same capability over plain HTTP is in the translate API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?