Skip to main content
Glama
Sign In
CleanWeb x402 — Smart Web Scraping & YouTube AI Agent

CleanWeb x402 — Smart Web Scraping & YouTube AI Agent

by nohosa001-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

extract_json_schema

Extract schema-constrained JSON data from any webpage using Gemini AI. Provide a URL and schema description to get clean, structured attributes like pricing or specs.

Instructions

Extracts schema-constrained structured JSON data from any webpage using Gemini AI (0.030 USDC).

Usage Guidelines:

  • Use when an agent needs structured attributes (e.g. pricing, specs, event dates) directly from a URL.

  • Returns: Clean JSON dictionary matching the requested schema description.

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>",
      "schema_description": "<schema_description>"
    },
    "name": "extract_json_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget webpage URL to extract JSON from.
auth_token_or_txNoOptional x402 auth token or tx hash.
schema_descriptionYesDescription or format of the fields to extract (e.g., 'price, product_name, in_stock').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.6
  2. Removedv1.2.5
  3. Addedv1.2.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the underlying model (Gemini AI) and the cost (0.030 USDC), which is real behavioral value. However, it says nothing about auth/payment requirements despite an auth_token_or_tx parameter, nor about rate limits or failure behavior.

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 one-line purpose followed by clearly labeled Usage Guidelines and Returns sections. Every line is relevant; it is tight and scannable with no filler.

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?

An output schema exists, so return-value detail is not required. The description covers purpose, usage context, cost, and return shape, which is sufficient for invocation. The main missing piece is any note on the payment/auth flow implied by auth_token_or_tx.

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 100%, so all three parameters are already documented in the schema, making baseline 3 appropriate. The description restates the 'schema_description' concept and the JSON return but adds no syntax or format detail beyond the schema.

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?

Names a specific verb and resource: 'Extracts schema-constrained structured JSON data from any webpage,' and adds distinguishing detail (Gemini AI, 0.030 USDC). It does not explicitly differentiate itself from close siblings like clean_web_content, search_web_quick, or deep_research_topic, but the purpose is unambiguous.

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

Usage Guidelines4/5

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

An explicit 'Use when...' condition with concrete examples (pricing, specs, event dates) directly from a URL. It lacks any when-not-to-use guidance or named alternatives among the many sibling web/content tools, so it stops short of the top score.

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

Deploy Server

Other Tools