Skip to main content

MCP Tools Reference

The Ollang MCP server exposes the following tools, grouped by category. Each tool maps to one or more endpoints in the Ollang Integration API — MCP simply gives your AI assistant a natural-language interface to them.

File Management

Upload files for processing and translation. Supports videos (MP4, AVI, MOV), documents (PDF, DOCX), images in JPEG, JPG, or PNG for Image to Image translation, audio files, subtitles, JSON, and DITA/XML content.Parameters:
Provide exactly one of url, base64Content, content, or ditaContent — one source per upload. Base64 payloads travel through the AI assistant’s context, so prefer url for files larger than a few megabytes, and pass expectedSize and/or sha256 with base64Content so uploads fail loudly if the data is corrupted in transit.
Upload a VTT subtitle file for a project, from WebVTT content or a URL.Parameters:
Provide exactly one of vttContent or url.
Start an upload session for binary files too large to send inline in one tool call. Returns an uploadId plus a direct PUT uploadUrl — the preferred path is to PUT the raw file bytes to that URL with any HTTP client, so the file never passes through the AI assistant’s context.Parameters:
Sessions expire after 60 minutes. As a fallback when no HTTP client is available, send the file’s base64 in pieces with appendUploadChunk, then call finalizeChunkedUpload.
Send one base64 piece of a chunked upload session (fallback path). Chunks are consecutive substrings of the file’s full base64 string.Parameters:
Assemble all chunks of an upload session, verify integrity (size and optional SHA-256), and upload the file to Ollang. Returns the new projectId.Parameters:
Discard a chunked upload session and its stored chunks without uploading.Parameters:

Order Management

Create a new translation or transcription order.Parameters:
language should be a code from the supported-languages catalogue — pass the exact code returned by getSupportedLanguages or validateLanguageTag rather than guessing a region subtag (Brazilian Portuguese is pt, not pt-BR; pt-PT is Portugal). Ollang’s API itself accepts any well-formed BCP-47 tag beyond the catalogue and falls back to the closest supported match (typically the primary language subtag) when a regional variant isn’t directly recognized — catalogue codes are the ones with verified full provider coverage.
proofreading, revision and other are legacy or system-generated order types. They may appear on existing orders and are accepted by the getOllangOrders type filter, but they cannot be created through this tool.
Fetch orders with pagination, search, sorting, and filters. Each order includes its overallQualityScore when a QC evaluation has completed.Parameters:
Get detailed information about a specific order including QC results.Parameters:
Cancel an existing order.Parameters:
Re-run an order to regenerate the translation with current AI models.Parameters:
Request subtitle embedding for an order to burn (hardcode) the translated subtitles directly into the video file.Parameters:
Export video timestamps, transcriptions, and translations for an order as an XLSX spreadsheet. Returns a short-lived download URL (expires after 60 minutes) — the file bytes never pass through the AI assistant’s context.Parameters:

Quality Control

Run an AI-powered quality control evaluation on an order.Parameters:
Check whether an order is paused at a review gate, and if so which team tag owns it, the review type (comment or assignment), when it entered review, and who can review it. Use this when an order sits in the review status to find out who is blocking it.Parameters:
Escalate an order for manual review by a human translator.Parameters:
Cancel an active human review request. Reverts a Level 1 (Human Review) order back to Level 0 (AI-only), refunds the human review credits, and disconnects the assigned translator. Only Level 1 orders with status ongoing can be cancelled.Parameters:

Revisions

Report issues or request changes to delivered content.Parameters:
Retrieve all revision requests for an order.Parameters:
Delete a specific revision request.Parameters:

Projects

Retrieve all projects with pagination, search, and sorting.Parameters:
Get detailed information about a specific project.Parameters:

Custom Instructions

Retrieve all custom translation instructions for your account.Parameters: None
Create a new reusable translation guideline.Parameters:
Update an existing custom instruction.Parameters:
Delete a custom instruction permanently.Parameters:
Retrieve suggested preset custom instructions (templates) to adopt or adapt as starting points for your own.Parameters: None

Folders

Retrieve all folders with pagination, search, and sorting. Folders organize projects — use a folder’s ID as the folderId parameter of uploadFile or beginChunkedUpload to place new projects in it.Parameters:
Get the distinct source/target language pairs from eligible orders in a folder. Use status=unassigned (default) for pairs available to assign to a translator, or status=assigned for pairs available to unassign.Parameters:
Batch assign a translator to all eligible (unassigned, completed) orders in a folder, optionally filtered by language pair. Returns the number of orders assigned.Parameters:
Batch unassign the translator from all eligible (assigned, ongoing) orders in a folder, optionally filtered by language pair. Returns the number of orders unassigned.Parameters:
Bulk export orders in folders as a single XLSX file with one sheet per order/language combination. Returns a short-lived download URL (expires after 60 minutes) — the file bytes never pass through the AI assistant’s context.Parameters:

Content Management

Export content translations as JSON, filtered by target language(s), tag(s), and order ID(s). Single-language exports return a flat key-value map; multi-language exports return a map grouped by language code.Parameters:
Import translation units (source + target text pairs) into your content database. Useful for bulk-loading translations from external systems or TMS exports.Parameters:

Translation Memory

A translation memory stores previously approved source/target pairs and reuses them on new orders. Create one, fill it with importMemoryItems, then pass its ID as selectedMemories on createOrder. Only document, subtitle/cc and Adobe AE orders consume them.
List all translation memories on the account, each with its stored translation-unit count.Parameters: none.
Create an empty translation memory.Parameters:
Retrieve a single translation memory, including how many translation units it stores.Parameters:
Rename a translation memory. Stored translation units are untouched.Parameters:
Permanently delete a translation memory and every translation unit in it.Parameters:
This cannot be undone.
Queue translation units for import into a memory. The import runs asynchronously through the same pipeline as dashboard uploads, including the vectorization that makes units available to semantic matching.Parameters:
The API accepts up to 1000 units per request, but MCP transports also cap a single tool call’s input — send a few hundred units per call and repeat for larger corpora. Poll getMemoryImportJob with the returned jobId for progress.
Check the progress of an import job. Reports both the import status and the separate vectorization step.Parameters:
Imported units are only available to semantic matching once vectorizationStatus is completed.

Billing and Credits

Both tools require the signed-in Ollang account to have the owner or billing-manager role (client_owner / client_accessBillings); other accounts receive a 403. Ollang MCP authenticates through OAuth, so this is a property of the account you signed in with — there is no API key to configure.
Get the account’s AI credit wallet: total, remaining, and used credits with their USD equivalents. Use this to check the balance before starting expensive work, or to explain an out-of-credits error.Parameters: none.
List AI credit consumption line items (one row per provider run) — the same data as the dashboard Consumption Breakdown export. Each line includes creditsUsed, usdEquivalent, provider, service, the requestor and program tags.Parameters:

Languages

List the languages Ollang supports, each with its regional variants. Use this to resolve a customer’s wording (“Brazilian Portuguese”) into the exact code createOrder expects — which is pt, since pt-PT is Portugal.Parameters:
Check a language code against the platform catalogue. Returns whether it is accepted, its parsed language and region, and the reasons it failed.Parameters:
createOrder, uploadFile, and project creation expect a code from the supported-languages catalogue for guaranteed full coverage — check here whenever a code is uncertain, especially before assuming a region subtag such as pt-BR exists. Ollang’s API also accepts any well-formed BCP-47 tag beyond the catalogue, falling back to the closest supported match (typically the primary language subtag) when a regional variant isn’t directly recognized.

Utilities

Check the health status of the Ollang API.Parameters: None
Download and parse subtitle files from URLs. Supports SRT, VTT, ASS, and SSA formats.Parameters:
Download and parse JSON files from URLs.Parameters:
Download and parse DITA/XML documentation files from URLs.Parameters: