Crawlora MCP

whatnot_seller

Read-only

Get a public Whatnot seller profile and one page of the seller's livestreams. Pass next_cursor back as cursor while has_more is true. Does not include shop products.

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": {
      "username": "<username>",
      "cursor": "<cursor>"
    },
    "name": "whatnot_seller"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	Yes	Opaque cursor from a prior response's next_cursor
`username`	Yes	Whatnot seller username

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Opaque cursor from a prior response's next_cursor"
```
- addedInput schema / properties / username / description
```
Added value: +"Whatnot seller username"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so safety is covered without the description. The description adds real behavioral detail the annotations lack: results are public, only one page of livestreams is returned, and the response carries next_cursor/has_more for continuation, plus the explicit scope exclusion of shop products.

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?

Three sentences, zero filler: identity/scope first, pagination handling second, exclusion last. Everything is front-loaded and each sentence carries distinct information.

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?

With an output schema present it needn't describe return values, and annotations cover the safety profile. The description supplies scope exclusions and the pagination loop, leaving only the sibling-routing question unaddressed — a small gap for a two-param tool.

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% and the schema already explains that cursor is an 'Opaque cursor from a prior response's next_cursor.' The description's pagination sentence largely restates that relationship, adding no new syntax or format detail, so the baseline 3 applies.

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 gives a specific verb and resource ('Get a public Whatnot seller profile and one page of the seller's livestreams') and sets scope with the exclusion 'Does not include shop products.' It implicitly separates itself from whatnot_live (livestreams without a seller scope) but never names a sibling, so it stops short of the 5 bar.

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?

It gives an explicit operational rule for pagination: 'Pass next_cursor back as cursor while has_more is true.' That tells the agent how to continue retrieval across pages, though it offers no guidance about when to choose this tool over whatnot_live or whatnot_browse.

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

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