Skip to main content
Glama
Analog-Labs

Firestarter MCP Server

by Analog-Labs

firestarter_update_listing

Update a marketplace listing's product details, inventory, status, photos, variants, and more. Correct fields, pause or reactivate listings, or activate imported drafts.

Instructions

Update a listing's product details — name, description, category, inventory, status, brand, condition, sku, return policy, dispatch time, country of origin, physical dimensions/weight, materials, tags, or variants. Use this to rename a product, change its description, update stock levels, pause/reactivate a listing, or fill in/correct any of those detail fields. Also activates imported drafts (status 'active') - drafts need a positive price and at least one photo. High-value (>= $500) and luxury-category drafts additionally require a possession-verification photo: activation returns the instructions and an FS-XXXX code for the seller, and firestarter_verify submits the seller's photo. For pricing changes, use firestarter_reprice instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoSeller's own inventory/stock-keeping code for this listing. Distinct from any barcode/UPC — seller-internal, never shown to buyers.
tagsNoFreeform search/discovery tags, e.g. ['summer', 'unisex'].
brandNoManufacturer or brand name, e.g. 'Logitech'.
statusNoNew listing status
categoryNoNew category (e.g. 'sports/tennis')
variantsNoSize/color/option variants for display and inventory tracking (not a checkout-level construct — orders still resolve at the listing level).
width_inNoPackaged width, in inches.
conditionNoItem condition. Omit for new/unspecified.
height_inNoPackaged height, in inches.
length_inNoPackaged length, in inches.
materialsNoMaterials the item is made of, e.g. ['cotton', 'polyester'].
weight_ozNoPackaged weight, in ounces.
image_urlsNoReplace the listing's photos with these public image URLs. If the seller attached a photo in this conversation, call firestarter_upload_image FIRST (pass its hosted URL as image_url — never rebuild it as a base64 data-URI) to get a permanent URL, then pass it here. Never ask them to re-send a photo already in the conversation.
listing_idYesThe listing ID to update
video_urlsNoProduct video URLs (MP4 or WebM, up to 25 MB and about 60 seconds each, max 3). The server fetches and re-hosts each one, so pass any public https URL — there is no separate upload step and no base64 form: a 25 MB video does not survive being emitted as a tool argument. Omit to leave existing videos untouched; pass an empty array to remove them. Videos are shown alongside the photos on the listing page and the share page.
descriptionNoNew product description
product_nameNoNew product name/title
inventory_qtyNoUpdated inventory quantity
return_policyNoFree-text return policy shown to buyers, e.g. '30-day returns, buyer pays return shipping.'
ship_time_daysNoTypical number of days from order to dispatch (handling time), not transit time.
allow_imagelessNoOverride the NEEDS_IMAGE activation gate and let this listing go live with no photo. Only pass true if the seller explicitly can't provide one right now.
fulfillment_modeNoHow orders for this listing get shipped. 'seller_managed' = NO platform label is ever bought: each paid order holds in awaiting_shipment until the seller ships it with their own carrier and enters tracking via firestarter_ship_order. 'platform' = the platform always books the carrier label. Pass null to clear back to auto (platform label when a carrier-ratable ship-from exists, otherwise seller-managed).
country_of_originNoISO 3166-1 alpha-2 country code where the item was made, e.g. 'US', 'VN'.
Behavior5/5

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

Annotations only signal that this is a mutating, non-destructive tool; the description adds substantial behavioral context beyond that: draft activation requires a positive price and photo, high-value/luxury drafts require a possession-verification photo with an FS-XXXX code flow, and activation returns instructions. It also clarifies that pricing changes belong on a different tool.

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?

The description is long but dense, and the core purpose is front-loaded before edge cases and routing notes. The second use-case sentence is slightly redundant with the opening field list, but each behavioral caveat (draft activation, high-value verification, reprice routing) earns its place.

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

Completeness5/5

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

For a 23-parameter mutation tool with no output schema, the description covers the important activation workflow, prerequisites, verification handoff, and alternative-tool routing. The schema fully documents the parameters, so nothing needed to invoke the tool correctly appears to be missing.

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 value by explaining that status='active' on imported drafts triggers activation requirements and by mapping field names like 'dispatch time' to their conceptual purpose. It doesn't need to duplicate schema detail, but the activation semantics for 'status' go beyond the schema's bare 'New listing status'.

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?

The description starts with a specific verb and resource — 'Update a listing's product details' — and enumerates the exact fields it can modify. It also explicitly distinguishes itself from firestarter_reprice and firestarter_verify, so an agent can tell this tool apart from related siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete when-to-use scenarios: rename, change description, update stock, pause/reactivate, fill/correct fields, and activate imported drafts. It also names exclusions — pricing changes go to firestarter_reprice and verification photos go to firestarter_verify — leaving little to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Analog-Labs/firestarter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server