Skip to main content
Glama
PageTranslate MCP Server

PageTranslate MCP Server

Official

Download a finished translation

download_translation
Idempotent

Save the translated file from a completed translation job to your computer in its original format without overwriting existing files. Specify a job ID and optional output folder.

Instructions

Save the translated file of a completed job to this computer. It has the same format as the source (PDF, DOCX, EPUB or image). Never overwrites an existing file.

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": "download_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
output_dirNoFolder to save into, usually the source file's folder. Defaults to the server's working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the saved file keeps the source format (PDF, DOCX, EPUB, image) and 'never overwrites an existing file,' which materially affects how an agent should call it repeatedly and is consistent with idempotentHint=true. It omits any mention of permissions, file naming, or what happens if the job isn't finished, but with annotations covering the safety profile this is solid coverage.

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?

Three short sentences, zero filler, with the action and format front-loaded and the non-overwrite guarantee placed last where it is most actionable.

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 simple two-parameter download with no output schema, the description covers what is saved, in what format, and the overwrite policy. The remaining gap is the failure mode when the job is not yet complete, which matters for an agent sequencing calls after start_translation.

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 coverage is 50%: output_dir is documented in the schema, while job_id has only a regex pattern. The description's 'completed job' adds a meaningful precondition on job_id, but it says nothing about output_dir's default or that the file lands in the server's working directory when omitted.

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 and resource ('Save the translated file of a completed job to this computer') and adds the format detail. It implicitly distinguishes itself from get_translation by producing a file on disk rather than metadata, though it never names that sibling to sharpen the contrast.

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?

The phrase 'of a completed job' implies a prerequisite (the job must be finished) and hints that this is the terminal step after start_translation. However, it never says what to do if the job is not complete, nor explicitly routes the agent away from get_translation for status checks.

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