Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Extract Product Data

web_extract_product
Read-onlyIdempotent

Extract product details like name, price, reviews, and ratings from product pages using AI-powered web scraping.

Instructions

Extract product information: name, price, reviews, ratings from any product page. Costs $0.05 USDC per request via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesProduct page URL to extract data from

Implementation Reference

  • The implementation of the 'web_extract_product' tool, which calls the 'apiPost' function to extract product information from the provided URL.
    async ({ url }) => {
      const data = await apiPost(`${WEB_EXTRACT_API}/api/v1/extract/product`, { url });
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • src/index.ts:353-368 (registration)
    Registration of the 'web_extract_product' tool, including its title, description, and input schema.
    server.registerTool(
      "web_extract_product",
      {
        title: "Extract Product Data",
        description: `Extract product information: name, price, reviews, ratings from any product page.
    Costs $0.05 USDC per request via x402 on Base.`,
        inputSchema: {
          url: z.string().url().describe("Product page URL to extract data from"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
      async ({ url }) => {
        const data = await apiPost(`${WEB_EXTRACT_API}/api/v1/extract/product`, { url });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations by disclosing the cost ('Costs $0.05 USDC per request via x402 on Base'), which is critical behavioral information not captured in structured fields. No contradiction with annotations exists.

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 extremely concise and front-loaded, with two sentences that efficiently convey purpose, data fields, and cost information. Every sentence earns its place by providing essential information without redundancy or fluff.

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?

Given the tool's moderate complexity (single parameter, no output schema), the description is largely complete. It covers purpose, specific data fields, and cost, but lacks details on output format, error handling, or rate limits. With annotations providing safety profile and schema covering parameters, the description is adequate though not exhaustive.

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?

The input schema has 100% description coverage, with the 'url' parameter fully documented. The description does not add any parameter-specific semantics beyond what the schema provides, such as URL format requirements or extraction limitations. With high schema coverage, the baseline score 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 clearly states the specific action ('Extract product information') and resource ('from any product page'), listing the exact data fields retrieved (name, price, reviews, ratings). It distinguishes itself from sibling tools like 'web_extract_metadata' or 'web_extract_structured' by focusing specifically on product data extraction.

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?

The description provides clear context for when to use this tool ('from any product page'), but does not explicitly state when not to use it or name specific alternatives. It implies usage for product data extraction versus general web extraction, but lacks explicit exclusions or comparisons to siblings like 'web_extract_batch' or 'web_extract_compare'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yantrix-ai/x402-apis-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server