Skip to main content
Glama

Web scrape

web_scrape
Read-only

Scrape any webpage and return clean text content. Strips HTML, scripts, and navigation. Returns the main content as readable text. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to scrape

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: HTML/script/navigation stripping, that the main content is returned rather than raw markup, and an explicit per-call price of $0.005 USDC. Annotations already cover read-only/open-world safety, so the remaining gap (rate limits, JS rendering, error behavior on blocked pages) is moderate.

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?

Four short, front-loaded sentences with no filler, and the cost warning lands early enough to matter. Minor redundancy between "return clean text content" and "Returns the main content as readable text" costs it the top slot.

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 one parameter, the description carries return-shape and cost information adequately. It stops short of covering failure modes and content size limits, which an agent spending real money per call would want to know.

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?

Single parameter with 100% schema coverage; the schema already documents `url` as "URL to scrape". The description adds nothing about accepted formats, query strings, or redirects, so this is the baseline case where structure does the work.

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 + resource ("Scrape any webpage") and immediately says what comes back ("clean text content", HTML/scripts/nav stripped). An agent can distinguish this from a search-style sibling, though it never names web_search as the way to discover URLs.

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?

Usage is only implied: scrape a page whose URL you already have. There is no explicit "use this when / don't use this when", no pointer to web_search for URL discovery, and no note on dynamic or JS-rendered pages that would fail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources