Agent workflow

Autonomous Listing Agent

Built on trial for Magic Hour. You send a product photo to a Telegram bot and get back a listing on eBay or Etsy that someone can check before it goes live.

View repository
  • Node.js
  • MCP
  • Claude API
  • OAuth 2.0
  • Cloudflare Workers
Timeline
Public repo · Aug 2026
Role
Independent developer
Scope
Node.js, MCP integrations, OAuth, marketplace APIs
Status
Built on trial for Magic Hour

What it does

The agent passes your photo to Magic Hour, pulls the generated product shots back down, and assembles what the marketplace needs. Creating the listing and publishing it are separate tool calls, so a person reads the title, description, price and images before any of it is public.

The repository holds the three MCP integrations behind that: eBay, Etsy, and a file service that hands out short public URLs for the cases where a marketplace wants to fetch an image rather than be given one.

What was hard

Most of the work was marketplace detail rather than agent logic. Both sides use OAuth 2.0, with PKCE where it is required, and they accept images in different ways, so each gets its own path. eBay also wants an account-deletion endpoint, which a Cloudflare Worker answers.

The context the agent carried was the other problem. I removed over a hundred redundant tool schemas and cut the framework’s 43 plugins to 7, all of which was being sent with every message to the model.

Where it goes next

Four live runs on eBay so far and one on Etsy. eBay is the better exercised of the two paths, so the next runs go to Etsy.

3Custom MCP integrations
43 → 7Framework plugins after audit
4Live eBay listing runs

Curious about something here? Ask me about it

Next projectTriangulate Rendering and optimisation · C++