Skip to main content
Glama

HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Web page extraction

hubvibe_extract_page
Read-onlyIdempotent

Web scraping / web page to clean text: any URL rendered in a real browser (JavaScript pages included) and returned as readable text with title, description and links. Use it to read an article, docs page or product page before summarising or extracting. Input: url. Raw status, headers and body: fetch.raw. A question answered from the page: research.brief. $0.10 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": "hubvibe_extract_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
languageNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
workerYes
price_usdYes
receipt_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / language / description
      Removed value: -"Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced."
    • removedInput schema / properties / url / description
      Removed value: -"http(s) URL to fetch."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / attribution
      Removed value: -{
      -  "items": {},
      -  "type": "array"
      -}
    • removedOutput schema / properties / billing_warning
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / provenance
      Removed value: -{
      -  "type": "object"
      -}
    • removedOutput schema / properties / receipt_id
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / status / type
      Removed value: -"string"
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "worker",
      -  "price_usd",
      -  "result",
      -  "provenance",
      -  "receipt_id",
      -  "receipt_url"
      -]New value: +[
      +  "status",
      +  "worker",
      +  "price_usd",
      +  "result",
      +  "receipt_url"
      +]
  2. Changed23 schema fields changed
    • removedOutput schema / description
      Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."
    • removedOutput schema / properties / attribution / description
      Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."
    • removedOutput schema / properties / attribution / items / description
      Removed value: -"A credit."
    • removedOutput schema / properties / attribution / items / properties
      Removed value: -{
      -  "text": {
      -    "description": "Credit.",
      -    "examples": [
      -      "Translated by Google"
      -    ],
      -    "type": "string"
      -  },
      -  "url": {
      -    "description": "Link.",
      -    "examples": [
      -      "https://translate.google.com"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / attribution / items / required
      Removed value: -[
      -  "text",
      -  "url"
      -]
    • removedOutput schema / properties / attribution / items / type
      Removed value: -"object"
    • removedOutput schema / properties / billing_warning / description
      Removed value: -"Present only when the charge was recorded with a caveat."
    • removedOutput schema / properties / billing_warning / examples
      Removed value: -[
      -  "settlement pending"
      -]
    • removedOutput schema / properties / price_usd / description
      Removed value: -"What this call cost, in USD."
    • removedOutput schema / properties / price_usd / examples
      Removed value: -[
      -  0.02
      -]
    • removedOutput schema / properties / provenance / description
      Removed value: -"How the result was produced: which providers ran and how long each took."
    • removedOutput schema / properties / provenance / properties
      Removed value: -{
      -  "attempts": {
      -    "description": "Provider attempts made, including retries and failovers.",
      -    "examples": [
      -      1
      -    ],
      -    "type": "integer"
      -  },
      -  "elapsed_ms": {
      -    "description": "Wall-clock milliseconds for the whole job.",
      -    "examples": [
      -      340
      -    ],
      -    "type": "integer"
      -  },
      -  "providers_used": {
      -    "description": "Providers that served the job.",
      -    "examples": [
      -      [
      -        "coinbase-advanced-trade-public"
      -      ]
      -    ],
      -    "items": {
      -      "description": "Provider name.",
      -      "examples": [
      -        "coinbase-advanced-trade-public"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "steps": {
      -    "description": "Every step the job ran, in order.",
      -    "items": {
      -      "description": "One step of the job.",
      -      "properties": {
      -        "ms": {
      -          "description": "Milliseconds the step took.",
      -          "examples": [
      -            312
      -          ],
      -          "type": "integer"
      -        },
      -        "ok": {
      -          "description": "Whether the step succeeded.",
      -          "examples": [
      -            true
      -          ],
      -          "type": "boolean"
      -        },
      -        "provider": {
      -          "description": "Provider that served the step.",
      -          "examples": [
      -            "coinbase-advanced-trade-public"
      -          ],
      -          "type": "string"
      -        },
      -        "reason": {
      -          "description": "Failure reason, on a failed step.",
      -          "examples": [
      -            "provider_timeout"
      -          ],
      -          "type": "string"
      -        },
      -        "step": {
      -          "description": "Step name inside the worker.",
      -          "examples": [
      -            "quote"
      -          ],
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "step",
      -        "ok",
      -        "ms"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  }
      -}
    • removedOutput schema / properties / provenance / required
      Removed value: -[
      -  "steps",
      -  "providers_used",
      -  "attempts",
      -  "elapsed_ms"
      -]
    • removedOutput schema / properties / receipt_id / description
      Removed value: -"Receipt id for this job."
    • removedOutput schema / properties / receipt_id / examples
      Removed value: -[
      -  "rcpt_9f1c2b3a4d5e6f70"
      -]
    • removedOutput schema / properties / receipt_url / description
      Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."
    • removedOutput schema / properties / receipt_url / examples
      Removed value: -[
      -  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
      -]
    • removedOutput schema / properties / result / properties
      Removed value: -{
      -  "description": {
      -    "description": "Meta description.",
      -    "examples": [
      -      "Example Domain for documentation."
      -    ],
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "final_url": {
      -    "description": "The URL after redirects.",
      -    "examples": [
      -      "https://example.com/"
      -    ],
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "javascript_rendered": {
      -    "description": "Whether a real browser rendered the page first.",
      -    "examples": [
      -      true
      -    ],
      -    "type": "boolean"
      -  },
      -  "links": {
      -    "description": "Up to 100 links on the page.",
      -    "examples": [
      -      [
      -        {
      -          "href": "https://www.iana.org/domains/example",
      -          "text": "More information..."
      -        }
      -      ]
      -    ],
      -    "items": {
      -      "description": "One link on the page.",
      -      "properties": {
      -        "href": {
      -          "description": "Absolute href.",
      -          "examples": [
      -            "https://example.com/pricing"
      -          ],
      -          "type": "string"
      -        },
      -        "text": {
      -          "description": "Anchor text.",
      -          "examples": [
      -            "Pricing"
      -          ],
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "href"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "text": {
      -    "description": "Readable text of the page.",
      -    "examples": [
      -      "Example Domain. This domain is for use in illustrative examples..."
      -    ],
      -    "type": "string"
      -  },
      -  "text_chars": {
      -    "description": "Characters in `text`.",
      -    "examples": [
      -      172
      -    ],
      -    "type": "integer"
      -  },
      -  "title": {
      -    "description": "Page title.",
      -    "examples": [
      -      "Example Domain"
      -    ],
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "truncated": {
      -    "description": "Whether the text was cut at the extraction limit.",
      -    "examples": [
      -      false
      -    ],
      -    "type": "boolean"
      -  },
      -  "url": {
      -    "description": "The URL requested.",
      -    "examples": [
      -      "https://example.com"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / result / required
      Removed value: -[
      -  "url",
      -  "text",
      -  "text_chars",
      -  "truncated",
      -  "links",
      -  "javascript_rendered"
      -]
    • removedOutput schema / properties / status / description
      Removed value: -"Present only on a delivered result."
    • removedOutput schema / properties / worker / description
      Removed value: -"Catalog name of the worker that ran."
    • removedOutput schema / properties / worker / examples
      Removed value: -[
      -  "market.quote"
      -]
    • removedOutput schema / title
      Removed value: -"extract.page response"
  3. Changed1 schema field changed
    • addedOutput schema / properties / attribution
      Added value: +{
      +  "description": "Present only when the result's text was machine-translated: the credit to show with it.",
      +  "items": {
      +    "description": "A credit.",
      +    "properties": {
      +      "text": {
      +        "description": "Credit.",
      +        "examples": [
      +          "Translated by Google"
      +        ],
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Link.",
      +        "examples": [
      +          "https://translate.google.com"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "text",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.",
      +  "maxLength": 35,
      +  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on all 38 routes. A receipt for the job is at `receipt_url`."New value: +"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."
  6. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and open-world behavior, and the description adds real value beyond them: JavaScript rendering in a real browser, the shape of what comes back (title, description, links), and an explicit $0.10 per-call cost. It stops short of disclosing failure modes such as blocked or paywalled pages, timeouts, or how long a render takes, which keeps it from a 5.

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-loads the core capability, then routes alternatives and cost in short labeled fragments with no filler. The telegraphic 'Raw status, headers and body: fetch.raw' style is efficient, though the fragment grammar makes the sentence boundaries slightly harder to parse than prose would.

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

Completeness3/5

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

An output schema exists, so return values need not be detailed, and annotations plus the cost note cover the safety and commercial picture. The one substantive hole is the undocumented 'language' parameter, and there is no note on pagination, dynamic content that loads after scroll, or what happens with non-HTML URLs.

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 coverage is 0%, so the description must carry parameter meaning, but it only says 'Input: url.' The optional 'language' parameter (with its 2-3 letter pattern and 35-char limit) is never mentioned, leaving the agent to guess whether it controls rendering locale, output language, or Accept-Language headers.

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 a concrete verb and resource ('web scraping / web page to clean text') plus the mechanism (rendered in a real browser, JavaScript included) and the output shape (readable text with title, description and links). It also explicitly differentiates itself from hubvibe_fetch_raw (raw status/headers/body) and the research path, so an agent can pick it without opening the schema.

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?

Gives a clear when-to-use rule ('read an article, docs page or product page before summarising or extracting') and names two alternatives with the condition that selects them: fetch.raw for raw response data and research.brief for a question answered from the page. Exclusions and routing are both present.

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.