Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

whatnot_seller

Fetch a Whatnot seller's public profile and one page of livestreams, using next_cursor pagination; shop products aren't included.

Instructions

Get a Whatnot seller profile and shows. Returns public seller profile details and one page of the seller's livestreams. Use next_cursor as cursor to continue while has_more is true. The endpoint 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>"
    },
    "name": "whatnot_seller"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from a prior response's next_cursor
usernameYesWhatnot seller username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does reasonably well: it declares the return scope (public seller profile details, one page of livestreams), the pagination contract (cursor/next_cursor/has_more), and an explicit exclusion ('does not include shop products'). It leaves auth/permission requirements and rate limits unstated, which holds it below 5.

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?

Three tight sentences, front-loaded with purpose, then return contents, then pagination mechanics. Every sentence contributes; no filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns, and it only sketches them ('public seller profile details') without naming fields or the shape of the livestream page. The pagination contract and the products exclusion are covered, but the return-format gap is notable for a tool with zero output schema.

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 both parameters are documented in the schema, so the baseline is 3. The description's cursor guidance largely restates what the schema already says ('Opaque cursor from a prior response's next_cursor') and adds no new format or constraint details.

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?

States a specific verb and resource ('Get a Whatnot seller profile and shows') and immediately clarifies scope ('one page of the seller's livestreams'). Siblings like whatnot_browse, whatnot_categories, and whatnot_live exist but are not named, so differentiation is implied by domain (seller vs browse/categories) rather than explicit.

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?

Provides pagination guidance ('Use next_cursor as cursor to continue while has_more is true') which is real usage context, but gives no when-to-use versus alternatives (e.g., whatnot_live for browsing live streams) and no preconditions. Usage is implied from the purpose rather than stated.

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

Deploy Server

Other Tools