DocImprint

Translate URL

translate_url

Read-only

Fetch a public HTTPS URL and return its content translated into a target language. Lean mode — no bundle stored. Use when you need to understand web content in a different language. For extracting raw untranslated text, use extract_url instead. Returns: { url, translated_text, target_lang, truncated } Example prompts:

"Translate https://example.de/artikel into English for me."
"Translate this German article into Spanish: [URL]."
"Fetch [URL] and give me the French translation."

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public HTTPS URL to fetch and translate. Example: "https://example.de/artikel"
`max_tokens`	No	Input length cap (1 token ≈ 4 chars). Truncates fetched page content before translation. Example: 4000
`target_lang`	Yes	ISO 639-1 language code for the target language. Example: "es" for Spanish, "fr" for French, "de" for German, "ja" for Japanese, "zh" for Chinese

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`truncated`	Yes
`target_lang`	Yes
`translated_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026
RemovedJul 26, 2026

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "target_lang": {
+      "type": "string"
+    },
+    "translated_text": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "target_lang",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJun 24, 2026

changedInput schema / properties / max_tokens / description

Previous value: -"Input length cap (1 token ≈ 4 chars). Truncates fetched page content before translation."New value: +"Input length cap (1 token ≈ 4 chars). Truncates fetched page content before translation. Example: 4000"

changedInput schema / properties / target_lang / description

Previous value: -"ISO 639-1 language code, e.g. \"es\" (Spanish), \"fr\" (French), \"de\" (German), \"ja\" (Japanese)"New value: +"ISO 639-1 language code for the target language. Example: \"es\" for Spanish, \"fr\" for French, \"de\" for German, \"ja\" for Japanese, \"zh\" for Chinese"

changedInput schema / properties / url / description

Previous value: -"Public HTTPS URL to fetch and translate"New value: +"Public HTTPS URL to fetch and translate. Example: \"https://example.de/artikel\""

First observedJun 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond that: lean mode with no bundle stored (relevant given the get_bundle/verify_bundle siblings), an HTTPS-only public-URL constraint, and a truncated return field that warns output may be cut short.

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?

Front-loads the core capability, then the mode note, then the sibling routing, then the return shape. Example prompts are compact and each sentence carries usable information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with an output schema and full annotation coverage, the description supplies the missing pieces: fetch constraints, mode behavior, sibling routing, and the return shape. An agent has everything needed to invoke it correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by restricting url to public HTTPS endpoints and by framing truncation as a result-shaping concern rather than just a cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource with scope: 'Fetch a public HTTPS URL and return its content translated into a target language.' It explicitly distinguishes itself from the sibling extract_url, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives a clear use condition ('when you need to understand web content in a different language') and names the concrete alternative plus the condition that selects it ('For extracting raw untranslated text, use extract_url instead'). Nothing is left to inference.

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

All DocImprint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?