Skip to main content
Glama

scrape

Fetch a single web page and return its main content as clean Markdown or HTML, including title, links, and HTTP status. Enable JavaScript rendering for pages that require it.

Instructions

Fetch one web page and return its main content.

Returns title, content (Markdown by default; cleaned main HTML with format="html"; empty with format="links"), all links on the page, and the HTTP status code. Set render_js=True for pages that need JavaScript (needs the optional browser install).

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": "scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
formatNomarkdown
render_jsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose return shape, the format-dependent content behavior, and that render_js requires an optional browser install — useful operational context — but says nothing about rate limits, blocking/robots behavior, redirects, error results, or page-size limits.

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-loaded with a one-line purpose, followed by a compact return-value sentence and a single caveat about render_js. Dense but every sentence carries information; no filler or repetition.

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?

With no output schema and no annotations, the description does the heavy lifting by enumerating the return fields (title, content, links, status code) and format-specific behavior. Gaps remain around failure modes and request constraints, but an agent could call this correctly from what is given.

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 0%, so the description must compensate. It explains the three format enum values well (markdown default, cleaned main HTML, empty content with links) and clarifies render_js semantics, but adds nothing about the url parameter's accepted forms or constraints, leaving one required parameter entirely undocumented.

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

Purpose4/5

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

States a specific verb and resource ("Fetch one web page and return its main content"), with the "one web page" qualifier implicitly distinguishing it from the bulk-oriented crawl and map siblings. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Gives a conditional usage hint ("Set render_js=True for pages that need JavaScript") but never states when to choose this over crawl, search, or map, nor any exclusions such as unsupported page types or sites where scraping is disallowed. Usage is implied by the return-value list rather than stated.

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