SiteCheck Shop & Social

Nykaa beauty product search: name, brand, price and MRP

ecommerce_nykaa_beauty

Read-only

Nykaa (India) beauty product search: name, brand, price and MRP in INR, discount, rating, rating count, in-stock flag, shade/variant count, offer count, category path, tags (bestseller, featured) and product link, about 20 per page (page 1 to 10), plus the total found and the Nykaa listing the search maps to. From nykaa.com through a residential proxy. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "ecommerce_nykaa_beauty"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, e.g. 'lipstick', 'sunscreen', 'maybelline'
`page`	No	Results page 1 to 10 (default 1)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the data source and residential-proxy route, the pagination cap (page 1 to 10 at ~20 results per page), and — most importantly — the billing model: $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failures not charged. That cost and payment-rail disclosure is exactly the kind of auth/behavioral context annotations cannot express.

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 defining clause is front-loaded and the operational details (pagination, cost) are grouped at the end. The long enumeration of return fields is somewhat wasteful given an output schema exists, but the sentence remains single-purpose and readable.

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?

For a two-parameter read-only search with a full output schema and clear annotations, the definition covers source, pagination limits, and cost. The only real redundancy is restating return fields the output schema already provides, and there is no explicit routing to sibling retailer tools.

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 both parameters are already documented in structured form. The description only adds that a page holds about 20 results and that pages run 1 to 10, which is modest extra meaning over the schema's 'page 1 to 10 (default 1)'.

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 opens with a specific verb plus resource ('Nykaa (India) beauty product search') and names the retailer and country, which cleanly separates it from siblings such as ecommerce_sephora_products or ecommerce_openbeautyfacts_products. An agent knows exactly what corpus it queries 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 Guidelines3/5

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

Usage is only implied: an agent can infer it should call this for Nykaa/India beauty queries, and the schema examples ('lipstick', 'sunscreen', 'maybelline') reinforce query style. However, there is no explicit when-to-use guidance and no named alternative (e.g., Sephora or OpenBeautyFacts) for non-Nykaa or non-India needs.

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

All SiteCheck Shop & Social 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.

Resources

Need Help?