AllSearch MCP

Read a URL

fetch

Read-onlyIdempotent

Read one known URL and return its content: Hacker News, V2EX, and Stack Exchange threads via public APIs; other pages via Firecrawl. Report login walls, captchas, and paywalls without bypassing them.

Instructions

Read one known URL. Hacker News, V2EX and Stack Exchange threads are read through their public APIs with comment ids, authors, timestamps and replies; other pages through Firecrawl. Login walls, captchas and paywalls are reported, never bypassed.

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": {
      "url": "<url>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Absolute http(s) URL
`focus`	No	Optional words used to rank forum comments
`fresh`	No
`max_chars`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.3.0Oct 18, 2026
- addedInput schema / properties / focus / description
```
Added value: +"Optional words used to rank forum comments"
```
- addedInput schema / properties / max_chars / maximum
```
Added value: +200000
```
- addedInput schema / properties / max_chars / minimum
```
Added value: +100
```
- addedInput schema / properties / url / description
```
Added value: +"Absolute http(s) URL"
```
- addedInput schema / properties / url / maxLength
```
Added value: +4096
```
- addedInput schema / properties / url / minLength
```
Added value: +1
```
First observedv0.1.0Aug 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent and open-world, so the bar is lower; the description still adds real value by disclosing backend routing (public APIs for HN/V2EX/Stack Exchange vs Firecrawl elsewhere), the shape of forum results, and, most importantly, that login walls, captchas and paywalls are reported rather than bypassed. It omits rate limits and latency behavior.

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?

Two tightly packed sentences with the core action front-loaded and no filler. The second sentence is dense with site names but each clause carries distinct routing or failure information.

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?

An output schema exists, so return-value explanation is not required, yet the description still sketches forum output fields. For a read-only tool with only four parameters, the missing semantics of `fresh` and `max_chars` are the main remaining hole.

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 only 50%: `url` and `focus` are documented in the schema, but `fresh` and `max_chars` carry no description anywhere. The tool description compensates for none of that gap, so an agent cannot tell what `fresh` controls or how `max_chars` truncation behaves.

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 and resource ('Read one known URL') and implicitly distinguishes itself from the `search` sibling by scoping to a URL the caller already has. An agent can tell instantly this is the single-page reader, not a discovery tool.

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

Usage Guidelines4/5

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

The qualifier 'one known URL' tells the agent this is the right call when the link is already known, which points away from `search`, but no explicit when-not-to-use or alternative-by-name statement is given. The site-specific routing note further clarifies expected input shapes.

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

Deploy Server