Raise a bug with FLUF support. Two situations call for it, and the second is the one that gets missed:

1. The user describes a problem with FLUF that you can't resolve yourself.

2. YOU hit the problem — a FLUF tool keeps failing, returns something that contradicts itself or the user's account, or leaves you unable to finish the task. The user never has to mention it first, and being stuck is not a reason to keep retrying quietly. File the report, then tell the user what you filed. Don't file for things the user can fix themselves (expired token, lapsed plan, a channel needing reauthorisation) — tell them the fix instead. Their account identity is attached automatically — don't ask for it. Replies arrive in the user's FLUF inbox.

List the authenticated seller's FLUF products. Each row carries a vid — the product handle the crosslist tool takes — plus title, price, stock, source channel and the channels it is already live on.

Get the seller's orders across every connected marketplace, in one unified shape.

List existing FLUF products on one or more marketplaces. IMPORTANT: this is not always synchronous. Some channels are completed by the seller's own browser extension, so they come back queued and go live minutes later — report that honestly rather than telling the user the item is listed. Read status per channel in the response. Repeats of the same (product, channel) pair within 30s are ignored as accidental double-submits.

List the marketplace channels available on this account: which are already connected, and which this seller's plan can list to. Call this before crosslist rather than guessing channel names — the roster differs per account and changes over time.

Ask Intesa, the FLUF assistant that runs inside the seller's own account. Intesa can do things this MCP server cannot: diagnose why a channel stopped syncing, explain a listing error, run bulk jobs, search the seller's history and read FLUF's support docs. Prefer the direct tools (list_products, crosslist, get_orders) for simple reads and writes — they are faster and cheaper. Reach for this when the question is diagnostic or open-ended, e.g. 'why did my last five Vinted listings fail?'. Replies can take up to a minute because Intesa runs its own multi-step tool loop.