Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

whatnot_live

Read-only

A Whatnot live show's current shop feed: every product, auction, and giveaway listing currently visible, each with its seller's rating.

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": {
      "id": "<id>"
    },
    "name": "whatnot_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWhatnot live show id, e.g. from a browse result's id field

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Whatnot live show id, e.g. from a browse result's id field"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data reach are covered. The description adds genuine content-level context beyond that: the feed is a live, currently-visible snapshot mixing products, auctions, and giveaways, and each listing carries a seller rating. That tells the agent what to expect in terms of freshness and item mix, though nothing about pagination or result size.

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?

A single, front-loaded sentence that packs the resource, its live scope, its item types, and the seller-rating enrichment with no filler. Nothing is redundant and nothing important is buried.

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 one-parameter read tool with a full annotation profile and an output schema, the description covers what the tool returns and its live nature. The only thin spot is the absence of any usage routing against sibling Whatnot tools, which is a minor gap given the schema and output schema already carry the rest.

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 coverage is 100% and the single 'id' parameter is already documented in the schema, including the hint that it comes from a browse result's id field. The description contributes no additional meaning about the identifier, so the baseline 3 for a fully covered schema is appropriate.

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?

The description names a specific resource and its scope: a Whatnot live show's current shop feed containing products, auctions, and giveaways, each with the seller's rating. An agent can distinguish this from whatnot_browse, whatnot_categories, and whatnot_seller by the resource itself. It stops short of explicitly contrasting with those siblings, so it lands at a strong 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The phrase 'currently visible' hints that this is a live snapshot, but the agent gets no instruction on when this feed is preferable to whatnot_browse or whatnot_seller.

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

All Crawlora MCP toolsInspect
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