DocImprint

Extract Text from URL

extract_url

Read-only

Fetch a public HTTPS URL and return extracted text and page metadata. Lean mode — no evidence bundle stored, no bundle_id returned. Use for raw text extraction from web pages and online documents. Use summarize_url for summaries, qa_url for Q&A, translate_url for translation, extract_text for base64 file uploads. Returns: { url, title, word_count, text, final_url (after redirects) } Example prompts:

"Extract the text from https://example.com/report.pdf for me."
"Get me the raw content of this web page: [URL]."
"Pull the text from this online article so I can analyze it."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public HTTPS URL to fetch and extract. Example: "https://example.com/report.pdf" or "https://blog.example.com/article"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`text`	Yes
`title`	No
`final_url`	No
`word_count`	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": {
+    "final_url": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "word_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "url",
+    "text"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 24, 2026

changedInput schema / properties / url / description

Previous value: -"Public HTTPS URL to fetch and extract"New value: +"Public HTTPS URL to fetch and extract. Example: \"https://example.com/report.pdf\" or \"https://blog.example.com/article\""

First observedJun 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description goes beyond annotations by disclosing a key behavioral trait: 'Lean mode — no evidence bundle stored, no bundle_id returned.' It also notes the return shape including 'final_url (after redirects)', which is useful context. Annotations (readOnlyHint, openWorldHint) cover safety and external interaction, but the description adds operational specifics about storage behavior and output. It could mention rate limits or auth requirements, but the core behaviors are well-covered.

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?

The description is tightly structured: first sentence states the core action and output format, second sentence clarifies the 'lean' behavioral distinction, third sentence lists alternatives, and then a separate 'Returns' block and example prompts. Every sentence adds value, and information is front-loaded.

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?

Given the tool's simplicity (1 parameter, output schema exists), the description provides complete context: it explains the lean mode, lists the return fields, and positions the tool within the sibling ecosystem. The agent has everything needed to call it correctly and understand its output.

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 description coverage is 100%, and the single parameter is fully documented in the schema with format and examples. The description adds no new parameter-level details, which is appropriate given the schema's completeness. Baseline 3 is correct when the schema already provides full semantic coverage.

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?

The description uses a specific verb ('Extract') and resource ('text from URL'), and it clearly distinguishes itself from siblings by naming the exact alternatives for different operations (summarize_url, qa_url, translate_url, extract_text). An agent can immediately tell this is raw text extraction without any summarization or Q&A.

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?

It explicitly states when to use this tool ('raw text extraction from web pages and online documents') and provides a clear mapping to alternatives for other intents (summarize_url for summaries, qa_url for Q&A, translate_url for translation, extract_text for base64 uploads). This is comprehensive routing guidance with no inference required.

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?