Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

reverb_shop

Fetch a Reverb shop's public profile and current active listings by slug, with optional keyword filter, page, and limit.

Instructions

Get a Reverb shop's profile and active listings. Returns a Reverb shop's public profile plus a page of its current active listings (Reverb's own "shop" view of a seller). slug is the shop's slug, from a listing's own shop link or reverb.com/shop/{slug}. query is an optional free-text filter scoping the listings sub-page to a keyword within that shop. An unknown slug returns a typed not-found error.

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": {
      "slug": "<slug>"
    },
    "name": "reverb_shop"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page number for the shop's listings, defaults to 1
`slug`	Yes	Shop slug
`limit`	No	Listings per page, defaults to 24, maximum 50
`query`	No	Free-text filter scoping the shop's own listings sub-page

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.13Oct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses that this is a retrieval of a public profile plus current active listings, and that an unknown slug returns a typed not-found error. It does not mention permissions, rate limits, or side effects, but the read-oriented behavior is clear from 'Get' and the return description.

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?

Four sentences, front-loaded with purpose and return shape, then slug source, query behavior, and error behavior. There is no redundant or wasted text.

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 four-parameter read tool with no annotations or output schema, the description covers purpose, return composition, required slug source, query scope, and not-found behavior. Pagination and limit details are left to the schema, which is reasonable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds useful meaning for slug by identifying its source from a listing's shop link or reverb.com/shop/{slug}, and clarifies that query scopes only the listings sub-page.

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?

States a specific verb and resource: gets a Reverb shop's public profile plus a page of its active listings. It also distinguishes this as Reverb's own 'shop' view of a seller, which clarifies its role among sibling tools.

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?

Explains how to obtain the required slug and what the optional query does, implying usage for shop-level retrieval. However, it does not explicitly compare this tool with alternatives such as reverb_search or reverb_shop_feedback, so the agent must infer when this is preferable.

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

Deploy Server