Skip to main content
Glama
Analog-Labs

Firestarter MCP Server

by Analog-Labs

firestarter_list

Create a product listing on Firestarter instantly with just a name and USD price. Optional details like photos, variants, and shipping policy can be added later as refinements.

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 — do NOT interrogate the seller for category, inventory, shipping, or ship-from. Create the listing immediately with what you have, then tell them what defaulted and how to refine it. 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 — offer these as refinements, don't demand them up front. If the seller already sent a photo in the conversation, reuse that URL in image_urls — never ask them to re-send it. The listing goes live instantly unless something blocks activation (e.g. payouts not connected), 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 to get a hosted 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.
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.
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 minimal annotations (readOnlyHint=false, destructiveHint=false) by disclosing defaults (inventory unlimited, ship-from account default, worldwide shipping, duties disclosure for cross-border), activation behavior (instantly live vs. draft with fix list), and the instruction to reuse photos already in conversation. It also explains shipping is estimated live and sellers no longer set flat rates, matching the schema's deprecation note. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although long, every sentence earns its place. The description is front-loaded with the essential behavior ('ONLY two fields are required') and then structures the rest into defaults, optional refinements, photo handling, activation, and sibling alternatives. There is no filler or redundancy—just dense, actionable information appropriate for a 27-parameter tool.

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?

The description is remarkably complete for the tool's complexity: it covers defaults, activation, photo reuse, shipping policy, and alternatives. However, there is no output schema, and the description only hints at the success response ('tell them what defaulted and how to refine it') rather than describing the return format. For a create tool with a complex side-effect, a bit more detail on the success response (e.g., listing ID) would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds significant value beyond the schema by grouping parameters, stating only two are required, explaining defaults for omitted fields, and giving tactical guidance like 'don't ask for category' and 'If the seller already sent a photo, reuse that URL in image_urls.' This is more than just restating the schema; it tells the agent how to handle all 27 parameters in a real conversation.

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+resource: 'List (create) a product for sale on Firestarter.' It also distinguishes from siblings by explicitly directing 'To VIEW or edit listings you already have, use firestarter_listings / firestarter_update_listing instead; to BROWSE other sellers' products, use firestarter_catalog_search.' This is a clear, unambiguous purpose with sibling differentiation.

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 when-to-use guidance: 'Create the listing immediately with what you have' and 'do NOT interrogate the seller for category, inventory, shipping, or ship-from.' It also states when not to ask for optional fields, how to handle existing photos, what to do if activation is blocked, and names alternative tools for viewing/editing/browsing. This is exemplary usage guidance.

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