Skip to main content
Glama
Analog-Labs

Firestarter MCP Server

by Analog-Labs

firestarter_list

Create a Firestarter product listing with just a name and USD base price; optional details can be added later, and it goes live instantly unless a photo is missing.

Instructions

List (create) a product for sale on Firestarter. ONLY two fields are required: product_name and base_price (USD). Everything else is OPTIONAL with sensible defaults, so a listing can be created from minimal information and refined afterwards; the response echoes the resulting settings. Defaults when omitted: inventory unlimited, shipping = estimated live at checkout by the delivery provider (based on the buyer's destination; sellers no longer set a flat/free rate), ship-from = account default address, ships worldwide (cross-border buyers get a duties disclosure; restrict with shipping_policy). Also optionally settable: brand, condition, sku, return policy, dispatch time, country of origin, physical dimensions/weight, materials, tags, and size/color variants — all of them can be filled in later with firestarter_update_listing. image_urls accepts a photo URL already available in the conversation (e.g. one returned by firestarter_upload_image). The listing goes live instantly unless something blocks activation (e.g. no product photo yet — see allow_imageless), in which case it's saved as a draft and the response lists exactly what to fix. To VIEW or edit listings you already have, use firestarter_listings / firestarter_update_listing instead; to BROWSE other sellers' products, use firestarter_catalog_search.

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'.
categoryNoOptional. Product category (e.g. 'electronics/audio/earbuds'). Infer a reasonable one from the product name if obvious; otherwise omit — don't ask.
shippingNoDeprecated and ignored — shipping is always estimated live from a delivery service provider based on the buyer's destination; sellers no longer set a flat/free shipping price. Accepted for backward compatibility only.
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'].
ship_fromNoShip-from (origin) address — where this item ships FROM. Used to compute real shipping rates (#332). Omit to use your account's default fulfillment address.
weight_ozNoPackaged weight, in ounces.
base_priceYesREQUIRED. Sale price in USD, e.g. 49.99.
image_urlsNoPublic product photo URLs (first is the primary image). 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.
source_urlNoOptional. If the seller mentions or pastes a link to their OWN existing listing for this product elsewhere (their Etsy/eBay/Shopify page, etc.), pass it here. Firestarter will fetch it once and fill in whatever descriptive details (description, category, brand, materials, tags, condition) the seller didn't already give you — it never overwrites anything you explicitly set. Best-effort: if the fetch fails or finds nothing, the listing is still created normally.
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.
floor_priceNoNever sell below this price
product_nameYesREQUIRED. What's being sold, e.g. 'Logitech MX Master 3S Wireless Mouse'.
ceiling_priceNoNever surge above this price
inventory_qtyNoOptional. Available quantity. Omit for unlimited — don't ask the seller unless they mention stock limits.
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_duplicateNoCreate this listing even though the seller already has one with the same name. Only pass true if the seller confirms they genuinely want a second, separate listing.
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.
dynamic_pricingNoEnable demand-based pricing
shipping_policyNoWhere the seller is willing to ship this item. Omit to default to WORLDWIDE (ships anywhere the platform hard rules allow; cross-border buyers are shown a duties disclosure). mode 'domestic' = home country only; mode 'list' with countries:['CA','GB',...] = home country plus those ISO alpha-2 destinations; mode 'worldwide' (optionally exclude:['BR',...]) = everywhere except excluded codes. Sanctioned/embargoed destinations are always blocked regardless of this setting.
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. Omit for auto: platform label when a carrier-ratable ship-from exists, otherwise seller-managed. Pass 'seller_managed' when the seller says they ship orders themselves / with their own courier.
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?

The description goes far beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true). It discloses the go-live-vs-draft activation gate (e.g., NEEDS_IMAGE with allow_imageless override), the full default set when fields are omitted (unlimited inventory, live shipping estimates, account default ship-from, worldwide shipping), the duties disclosure for cross-border buyers, deprecated shipping behavior, source_url best-effort enrichment that never overwrites explicit values, and video re-hosting semantics. No contradiction with annotations.

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 earned: it front-loads purpose and the required-only contract, then covers defaults, activation behavior, image workflow, and sibling routing in dense prose. The one mildly redundant passage is the enumeration of optional settable fields ('brand, condition, sku...'), which the schema already documents, but it serves as a useful orientation checklist for a 29-parameter tool, so it is not wasted.

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 complex tool with 29 parameters, nested objects, and no output schema, the description covers the critical non-obvious behaviors: the live-vs-draft activation outcome and that the response lists what to fix, the 'response echoes the resulting settings' return expectation, the upload-image prerequisite, and the source_url fill-in behavior. It leaves minor gaps such as validation-failure handling for malformed shipping_policy or ship_from objects, but the schema enums and per-field descriptions fill most of those, making this substantially complete.

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, but the description adds genuine cross-parameter meaning: it elevates product_name and base_price as the only required fields, explains default behavior for omitted inventory/shipping/ship-from/shipping_policy, clarifies the image_urls workflow dependency on firestarter_upload_image, and flags the shipping field as deprecated/ignored. These are semantics the schema descriptions do not convey on their own, though the heavy lifting for individual parameters still falls to the schema.

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 opens with a specific verb+resource pair ('List (create) a product for sale on Firestarter') and immediately constrains scope to the two required fields. It explicitly distinguishes itself from siblings by naming firestarter_listings (view), firestarter_update_listing (edit), and firestarter_catalog_search (browse others' products), so an agent cannot confuse it with adjacent tools even without opening their 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?

The description gives explicit routing: use firestarter_listings to view, firestarter_update_listing to edit/refine later, firestarter_catalog_search to browse other sellers, and firestarter_upload_image FIRST when a conversation photo needs a permanent URL. It also clarifies when to pass allow_imageless and allow_duplicate (only on seller confirmation), which is actionable selection guidance beyond the schema.

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