ebay-analyze

ebay-analyze is a command for Claude Code from jbwashington/ebay-mcp. It costs 7 tokens per session (361 once invoked), scanned A, original, MIT.

A command that examines item photos, identifies product details and condition, and prepares an eBay listing draft.

In plain words
What is it for?
Use it to identify brand, model, size, color, material, wear, flaws, measurements, and special features from photos, then create a title, description, keywords, condition grade, and item specifics.
Why use it?
It reduces the manual work of inspecting photos and turning scattered observations into consistent listing information. It also helps compare similar eBay items when researching price.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Part of the ebay-listing-automation plugin — 13 commands, 3 hooks shipped together

Good fit Use it to identify brand, model, size, color, material, wear, flaws, measurements, and special features from photos, then create a title, description, keywords, condition grade, and item specifics.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jbwashington/ebay-mcp/ebay-analyze
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/jbwashington/ebay-mcp

Made for: Claude Code.

Or install ebay-listing-automation, the plugin that ships this one along with the rest of its 13 commands, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ebay-analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/jbwashington/ebay-mcp/ebay-analyze.svg)](https://agentmods.dev/commands/jbwashington/ebay-mcp/ebay-analyze)
Your own site
<a href="https://agentmods.dev/commands/jbwashington/ebay-mcp/ebay-analyze"><img src="https://agentmods.dev/badge/commands/jbwashington/ebay-mcp/ebay-analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 361 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00361
Opus 5 $0.00003 $0.00180
Sonnet 5 $0.00001 $0.00072
Haiku 4.5 $0.00001 $0.00036

Measured 8d ago against content hash 993f67e4c113, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

ebay-analyze scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/ebay-analyze.md · 47 lines

What it actually says

Analyze eBay Item Photos

Analyze photos of an item to extract product details, condition, and create a listing draft.

Task

  1. Load all images from the folder: $1 (or ask user for path if not provided)

  2. Analyze the images to identify:

    • Brand and model
    • Category (sneakers, jacket, jeans, etc.)
    • Size (from tags)
    • Color/colorway
    • Condition (examine closely for wear, stains, flaws)
    • Any measurements shown in photos
    • Any visible flaws or defects
    • Material/fabric (from tags)
    • Special features (limited edition, collaboration, etc.)
  3. For sneakers specifically, check:

    • Outsole wear
    • Midsole condition (yellowing, cracking)
    • Upper condition (creasing, scuffs, stains)
    • Original box and accessories
    • Rate condition: DS, VNDS, 9/10, 8/10, etc.
  4. Create a structured analysis with:

    • SEO-optimized title (80 chars max)
    • Detailed description
    • Condition grade and details
    • List of any flaws
    • Suggested keywords
    • Item Specifics (aspects) as key-value pairs
  5. Use the eBay MCP tool ebay_search_by_image with the main product photo to find similar listings

  6. Use the eBay MCP tool ebay_search_by_keyword with brand + model to research pricing

  7. Suggest a competitive starting price based on similar listings

Output the complete analysis and ask if the user wants to create a draft listing.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 47 lines · 7 tokens per session scan A 993f67e4c113

Subscribe to this mod's changes

ebay-analyze is a command published in the GitHub repository jbwashington/ebay-mcp (13 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 361 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.