Skip to main content
Glama
kuraneko1

chrome-web-mcp

by kuraneko1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fetch_url

Fetch JavaScript-rendered public URLs and get readable, boilerplate-free markdown with final URL, redirect flag, and character count. Use it to validate search results or extract dynamic content.

Instructions

Fetch a public HTTP(S) URL with JavaScript rendering (Xvfb Chrome) and return shaped readable markdown plus requested/final URLs, redirect flag, and total_chars. The markdown is shaped (boilerplate removed, extraction method reported); if content looks missing, retry with format:text for the full rendered text. Use after google_search on result URLs, or for pages that need JS to render (SPAs, paywalled-after-consent layouts, etc.). Parallel calls are safe; each fetch uses its own tab. char_limit caps the returned text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic http(s) URL to fetch (no credentials, no localhost).
formatNomarkdown: shaped readable markdown, boilerplate removed. text: full rendered text, use when markdown looks incomplete. links: text plus follow-up link targetsmarkdown
char_limitNoMaximum characters of readable text to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Describes the rendering process (Xvfb Chrome), shaping behavior (boilerplate removed), and the return fields (requested/final URLs, redirect flag, total_chars). Lacks explicit error handling details but is otherwise transparent. No annotations provided, so description carries the burden.

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?

The description is moderately long but each sentence adds value. Some redundancy with char_limit but overall well-structured.

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?

Provides enough context for typical use: when to use, how to retry, parallel safety, and output shape. Could mention error cases but not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have clear descriptions: url includes security constraints (no credentials, no localhost), format enumerates options with meanings, char_limit defines range and purpose. Schema coverage is 100%.

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 exactly what it does: fetches a public URL with JS rendering, returns shaped markdown plus metadata. Distinguishes from sibling tools by mentioning use after google_search and for JS-heavy pages.

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?

Explicitly says when to use (after google_search, for SPA/paywalled pages), how to recover (retry with format:text), and notes parallel calls are safe. Also explains format alternatives.

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

Deploy Server

Other Tools