Overview

1. Get the make, model, condition, and any notable features from the user.
2. Call search_sold_listings with the make and model to get recent sold prices.
3. Call get_price_guide for Reverb's estimated value range.
4. Call search_listings with state=live to see current competition.
5. Compute the median of the last 10 sold prices. Count competing active listings.
6. Recommend a list price: median + 5-10% (room for offers). Factor in ~7.7% total fees (5% selling fee + 2.7% payment processing). Adjust for discontinued/rare gear (upper quartile) or successor-exists (lower quartile).
7. Read references/pricing_strategy.md for edge cases and advanced pricing tactics.

Always present: median sold price, price range, number of competitors, recommended list price, and estimated net after fees.

Listing Creation Workflow

When the user wants to list an item:

1. Gather: make, model, condition, price, description details, photos.
2. Call get_categories to resolve the correct category UUID.
3. Call get_listing_conditions to resolve the condition UUID.
4. Build an optimized title: [Brand] [Model] [Variant] [Color/Finish] [Year]. Keep it under 80 characters.
5. Draft a structured description: What It Is / Condition Details / What's Included / Shipping Info.
6. Call create_listing with all resolved fields. Set offers_enabled=true by default.
7. Always create as draft first. Never publish without user confirmation.
8. Present the draft for review. On confirmation, call publish_listing.

Read references/listing_optimization.md for title formulas, photo guidance, and category-specific tips.

Daily Seller Operations

When the user wants a status update or daily check-in:

1. Call get_orders_awaiting_shipment. List each order with item name and buyer.
   • Flag any order past the 1-business-day shipping SLA.
2. Call get_negotiations. List pending offers with item name, offer amount, and listing price.
3. Call get_messages with unread_only=true. List unread conversations.
   • Flag any message waiting more than 4 hours.
4. Present as a prioritized action list with counts.

Offer Handling

When evaluating an incoming offer:

1. Look up the listing price from the offer context.
2. Run sold comps: call search_sold_listings for the item.
3. Apply the decision framework:
   • >=85% of ask AND >=median sold → recommend accept
   • 70-85% of ask → recommend counter at 90% of ask
   • <70% of ask → recommend reject or hold firm
4. If the item has been listed >30 days, reduce thresholds by 5% (more flexibility for stale listings).
5. Present the analysis with the recommendation and reasoning.

To send an outgoing offer to a buyer (proactive offer): call send_direct_offer with listing_id and price. Optionally include shipping to offer free shipping as an incentive.

Post-Sale Workflow

After an order is placed:

1. Shipping: Call ship_order with carrier and tracking number. Set send_notification=true to email the buyer.
2. Communication: Send a thank-you message via reply_to_message.
3. Feedback: After delivery confirmation, call leave_feedback with a positive rating.
4. Bookkeeping: Call get_order_payments and get_payout_line_items to log:
   • Sale price
   • Selling fee (~5%)
   • Payment processing fee (~2.7%)
   • Shipping label cost (if applicable)
   • Net payout

Tool Quick Reference

Most-used tools with their required parameters:

Airtable Listing Tracker (Optional)

If airtable-mcp-server MCP tools (mcp__airtable__*) are available, you can sync Reverb listings to an Airtable base for inventory and sales tracking.

Recommended Schema

Single table called "Listings" with these fields:

Import Workflow

1. Call mcp__airtable__list_bases to identify the target base, then mcp__airtable__list_tables to find or confirm the Listings table.
2. Call find_my_listings with state=all and paginate through all pages.
3. For each listing, call mcp__airtable__search_records with filterByFormula matching Reverb ID to check for an existing record before creating or updating.
4. Map fields: Reverb state.slug → Airtable Status (draft → Draft, live → Live, ended → Ended, sold → Sold). Build URL as https://reverb.com/item/{slug}.
5. Call mcp__airtable__create_record for new items or mcp__airtable__update_records for existing ones.

Keeping It Current

• After creating or publishing a listing: create or update the Airtable record immediately.
• After a sale: update Status to Sold and populate Sold Date.
• Category is not returned by the listing list endpoint — populate it with a separate get_listing call per item, or fill it in manually.

Arbitrage & Deal Finding

Two prompts are available for identifying pricing opportunities:

find_arbitrage_deals

Use when you want to buy underpriced gear and resell at market. Two modes:

• Keyword mode: provide query (e.g. "Roland JX-08"). Runs one shared sold comps search, fast.
• Category browse mode: provide category_uuid (or category name; it resolves automatically). Scans newest listings in the category, per-item sold comps.

Results come back in a single deals list. Each entry has a no_comps flag:

• no_comps: false - compared against a price guide median. Has market_price, discount_pct, est_profit_usd. Sorted by profit.
• no_comps: true - no price guide median available (thin market). Shows the cheapest active listing for that model. market_price, discount_pct, est_profit_usd are null. Sorted by price after the comped deals.

Tips:

• Always pass condition= when you know the condition tier. Mixed-condition comps skew the median.
• Default threshold is 15% below median sold. Lower it to 10% for more results, raise to 20%+ for only clear deals.
• no_comps: true entries are not arbitrage-qualified - use them as a price floor reference, then verify with search_sold_listings.
• Read references/arbitrage.md for fee math, thin market handling, and when to skip a deal.

scan_my_listings_for_underpricing

Use when you want to audit your own active listings. Flags listings priced more than min_gap_pct% (default 10%) below the median sold price, with a suggested reprice.

Tips:

• Use category= to scope the scan when you have many listings to reduce first-run API call volume.
• A listing flagged that has been live > 30 days may have a demand problem (condition, photos, description) rather than a pricing problem.
• Profit estimates are pre-shipping-label. Adjust for heavy items manually.

Pitfalls

Encode these into every interaction:

• find_my_listings without state=all only returns live listings. Always default to state=all.
• Setting inventory=0 on any listing ends it immediately regardless of other flags.
• Shipping profiles cannot be created or modified via API — they must be set up manually at reverb.com/my/selling/shipping_rates.
• Ending a listing with reason=reverb_sale incurs a selling fee on the monthly bill.
• Photos are ordered by array position. First URL in the array = hero image.
• year field accepts fuzzy input: "1980s", "1979-1981", "mid 80s", "1959".
• Make and model are required for a draft to exist. If not provided, Reverb guesses from the title and may fall back to "Unknown" (which blocks publishing).
• publish=true can be included in the initial POST to skip the draft step — but prefer drafts for user review.
• B-Stock and Mint (with inventory) conditions require account-level eligibility.
• Only drafts can be deleted. Published listings (even if ended) cannot be deleted via API.
• Only Brand New, B-Stock, and Mint (with inventory) conditions support inventory > 1.
• Use photo_upload_method: "override_position" when reordering images via PUT.
• To purchase your own listings in sandbox for testing, you must use a separate sandbox account.