Skip to main content
Glama

Scrape a URL

scrape
Read-onlyIdempotent

Fetch a URL and return structured content in markdown or other formats; add a query to get only the top passages that answer it.

Instructions

Scrape a URL with source-aware routing and return structured content. formats defaults to ["markdown"]. With query, markdown and text are only the top_k passages that answer it.

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
modeNo
queryNo
top_kNo
dry_runNoNot supported here: leave it out and use the estimate tool to price a call.
formatsNo
optionsNoOther API fields for this operation, merged into the request body as they are (see the Clawifi API docs).
target_selectorNo
timeout_secondsNo
wait_for_selectorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.4.1
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": null,
      +  "description": "Not supported here: leave it out and use the estimate tool to price a call.",
      +  "title": "Dry Run"
      +}
    • addedInput schema / properties / formats
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Formats"
      +}
    • removedInput schema / properties / kwargs
      Removed value: -{
      -  "title": "Kwargs"
      -}
    • addedInput schema / properties / mode
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Mode"
      +}
    • addedInput schema / properties / options
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Other API fields for this operation, merged into the request body as they are (see the Clawifi API docs).",
      +  "title": "Options"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Query"
      +}
    • addedInput schema / properties / target_selector
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Target Selector"
      +}
    • addedInput schema / properties / timeout_seconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Timeout Seconds"
      +}
    • addedInput schema / properties / top_k
      Added value: +{
      +  "default": 5,
      +  "title": "Top K",
      +  "type": "integer"
      +}
    • addedInput schema / properties / wait_for_selector
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Wait For Selector"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url",
      -  "kwargs"
      -]New value: +[
      +  "url"
      +]
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that with a query, markdown and text return only the top_k answering passages — which materially changes what the agent will receive. It stays silent on rendering, timeout, selector waiting, and failure behavior, so the disclosure is partial.

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?

Three short sentences with the core action first and the output-shaping rules after; nothing is redundant. The phrase "source-aware routing" is unexplained jargon, which costs a point on clarity but not on length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 10-parameter, open-world tool with an output schema, and the description covers only a fraction of what an agent needs in order to call it well. Because return values are documented by the output schema, the missing pieces are the five undocumented parameters and the absence of any usage boundaries.

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 20% across 10 parameters, so the description is expected to compensate and largely does not. It clarifies formats default (markdown) and the interaction of query with top_k, but mode, options, target_selector, timeout_seconds, and wait_for_selector carry no explanation in either the schema or the description.

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?

The description opens with a specific verb and resource ("Scrape a URL") and states the outcome ("return structured content"), which is enough to distinguish it from siblings such as crawl, map_site, or search_free. It does not explicitly contrast itself with the closer alternatives fetch or extract, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over fetch, extract, crawl, or search_free, and no stated preconditions. The only routing hint ("use the estimate tool to price a call") lives in the dry_run schema field, not the description, so the description itself gives the agent no decision criteria.

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