Scrapling x402 Data Store

E-commerce price drops & restocks ($0.02)

ecom_changes

Read-only

PAID $0.02 USDC. Price drops, price rises, restocks, sell-outs, new products and removals detected between daily crawls of 180+ Shopify stores. Filter by type (comma list), domain, category, brand, days (1-30), limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ecom_changes"
  }
}

Input Schema

Name	Required	Description
`days`	No
`type`	No	price_drop,price_rise,restock,sellout,new_product,removed
`brand`	No
`limit`	No
`domain`	No
`api_key`	No	Optional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment'].
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / api_key / description

Previous value: -"Optional prepaid key (sk_scrapling_...). Otherwise pay per call with x402 via _meta['x402/payment']."New value: +"Optional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment']."

AddedOct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already indicate a safe read-only operation, but the description adds crucial behavioral context: the tool costs $0.02 USDC per call and accepts prepaid keys or x402 payment (via the api_key parameter). It also discloses data freshness (daily crawls) and scope (180+ stores), which are valuable beyond the annotations.

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?

The description is front-loaded with the cost and then efficiently packs the data scope and filter options into one dense sentence. There is no fluff, though the single-sentence filter list could be slightly more scannable.

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 complexity (7 optional params, no output schema), the description covers what the tool does, how to filter, and the payment model—enough for an agent to invoke it correctly. It lacks return format details, but for a simple list of change events that is a minor gap.

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?

With only 29% schema description coverage, the description partially compensates by listing all filterable fields (type, domain, category, brand, days, limit) and clarifying that 'type' is a comma list and 'days' ranges from 1-30. However, it does not explain the format or constraints for domain, brand, category, or limit, leaving gaps for an agent to interpret those parameters.

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 explicitly enumerates the exact change types (price drops, restocks, sell-outs, etc.) and the data source (daily crawls of 180+ Shopify stores), making it immediately distinguishable from sibling tools like ecom_product or ecom_snapshot. An agent can tell precisely what data this tool returns.

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?

The description lists filterable fields but gives no guidance on when to use this tool versus alternatives such as ecom_catalog, ecom_product, or free_ecom. There are no exclusions or prerequisites stated, leaving the agent to infer the appropriate context.

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

All Scrapling x402 Data Store tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.