Skip to main content
Glama
Sign In
PageTranslate MCP Server

PageTranslate MCP Server

Official
by Caravaca-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Start translating an uploaded document

start_translation
Idempotent

Starts translating an uploaded job using available plan words or credits; if the balance is insufficient, returns a payment URL and begins translation after payment.

Instructions

Start the translation of an uploaded job using the account's word balance (Pro plan words or credits). If the balance does not cover it, nothing is charged and the response carries a payment_url for the user to pay by card; translation then starts by itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "start_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation/non-destructive/idempotent profile, so the description is free to add the valuable parts: charging semantics, the all-or-nothing behavior when the balance is short, and the payment_url escape hatch with automatic restart. It does not address what happens on repeated calls for an already-started job, despite idempotentHint=true, which is the only real gap.

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?

Two sentences, front-loaded with the action and cost model, then the exception path. No filler or restatement of the title.

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?

With no output schema, the description does the right thing by disclosing the payment_url field present in the insufficient-balance response. It omits what a successful response looks like (e.g., job or translation ID to poll with get_translation), which is the remaining gap for a one-parameter async kickoff tool.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter job_id, and the description offers only the indirect hint that it refers to an "uploaded job." It never says the ID comes from upload_document or that it is a 24-hex ObjectId, so the schema carries nearly all the burden.

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 names a specific verb and resource ("start the translation of an uploaded job") and states the billing mechanism (word balance, Pro plan words or credits). It is clearly distinguishable from download_translation, get_translation, and list_translations, though it never names those siblings to route the agent explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by "uploaded job" (i.e., call after upload_document), but no explicit when-to-use/when-not-to-use guidance or prerequisite is stated. The insufficient-balance path is described well, which is a partial substitute for real routing guidance.

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

Deploy Server

Other Tools