Skip to main content
Glama

KillBounce Data

Web page plain text

fetch
Read-onlyIdempotent

Fetches a public URL and returns clean main-text content, title, meta description, status code, and final URL after redirects. Strips nav, ads, scripts, and boilerplate. Price: $0.005 USDC on Base per successful call (x402).

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

NameRequiredDescriptionDefault
urlYesPublic http(s) URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds useful operational context beyond annotations: it returns title, meta description, status code, and final URL after redirects; strips boilerplate; and costs $0.005 USDC per successful call. It does not cover failure behavior, content-type limits, or timeouts, but with annotations present this is substantial added transparency.

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

Conciseness5/5

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

The description is three tight sentences, front-loaded with what the tool does and what it returns. Each sentence earns its place by covering extraction behavior, boilerplate stripping, and pricing.

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, the description usefully lists the returned fields and explains that content is cleaned. For a simple one-parameter fetch tool with annotations covering safety, this is nearly complete, though it could mention error behavior or unsupported content types.

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?

There is one parameter and the schema already documents it at 100% coverage as a public http(s) URL. The description reinforces the public URL constraint but adds no syntax, format, or validation detail beyond the schema, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: fetches a public URL and returns clean main-text content plus metadata. It distinguishes this from general metadata or redirect tools by emphasizing extracted page text with nav, ads, scripts, and boilerplate stripped.

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 implied by the public URL constraint and the main-text extraction behavior, but the description does not explicitly say when to use this instead of siblings such as meta or redirects. It provides enough context to infer the basic use case, but no exclusions or alternative routing.

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