DocImprint

Summarize URL

summarize_url

Read-only

Fetch a public HTTPS URL and return a prose summary with key points. Lean mode — no bundle stored. Use when you need a condensed understanding of a web page. For raw text, use extract_url. For asking a specific question about a page, use qa_url. Returns: { url, summary, key_points: string[], truncated: boolean, word_count } Example prompts:

"Summarize https://en.wikipedia.org/wiki/Artificial_intelligence for me."
"Give me the key points from this blog post: [URL]."
"What is this article about? Summarize [URL]."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public HTTPS URL to fetch and summarize. Example: "https://en.wikipedia.org/wiki/Artificial_intelligence"
`max_tokens`	No	Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the output summary. Example: 4000

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`summary`	No
`truncated`	Yes
`key_points`	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": {
+    "key_points": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    },
+    "word_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "url",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedJun 24, 2026

changedInput schema / properties / max_tokens / description

Previous value: -"Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the output summary."New value: +"Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the output summary. Example: 4000"

changedInput schema / properties / url / description

Previous value: -"Public HTTPS URL to fetch and summarize"New value: +"Public HTTPS URL to fetch and summarize. Example: \"https://en.wikipedia.org/wiki/Artificial_intelligence\""

First observedJun 10, 2026

TDQS

A4.3/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 the safety profile is covered. The description adds genuinely useful context beyond that: 'Lean mode — no bundle stored', which matters given siblings like get_bundle/verify_bundle in the same family, and it declares the return shape. It stops short of noting rate limits, auth needs, or behavior on fetch failure, so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then alternatives, then return shape, then example prompts in a tight sequence. The example prompts are somewhat expendable, but they demonstrate correct phrasing and earn their place for a URL tool where input format matters.

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 two-parameter read-only tool with annotations covering safety and an output schema, the description is nearly complete: purpose, routing, mode, and return fields are all present. Only edge-case behavior (invalid/non-HTTPS URLs, fetch failures) is unaddressed.

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%, so both url and max_tokens are already documented in the schema, including the important note that max_tokens truncates input rather than output. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 ('fetch a public HTTPS URL and return a prose summary with key points') and explicitly distinguishes itself from two named siblings, extract_url and qa_url. An agent can pick this apart from the other URL tools without opening any 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 an explicit when-to-use ('need a condensed understanding of a web page') plus two when-to-use-something-else clauses routing to extract_url for raw text and qa_url for targeted questions. 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?