seller-assistant

Seller Assistant brings your Amazon wholesale workflow into your AI.

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

Get Account Context: Confirm that Seller Assistant is connected and return the authenticated user, current team, active plan, connected Amazon marketplaces, and remaining feature quotas. This tool req
List Price Lists: List the price lists the team has already analyzed, newest first. Use this whenever the user refers to an earlier analysis rather than a new one — "the list I uploaded last week", "m
Start Price List Analysis: Start analyzing a supplier price list to find profitable Amazon resale opportunities. When mapping a large source file, inspect only a few representative rows to confirm the

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Seller Assistant brings your Amazon wholesale workflow into your AI. Ask a question in plain language and get a real answer from your own account data.

RESEARCH A PRODUCT Look up any ASIN for sales rank, estimated monthly sales, Buy Box and competitor prices, Amazon fees, and warning flags such as meltable, oversize or hazardous. Add your cost and get profit, ROI and margin. Check whether your account is allowed to sell it before you buy.

FIND LEADS IN A SUPPLIER PRICE LIST Upload a supplier file and Claude analyses it, then shows the products worth buying. Filter by profit, ROI, sales rank, competition or brand. Check selling restrictions on the leads, then turn the ones you want into a purchase order.

FIND AND SAVE SUPPLIERS Search for wholesale suppliers and authorized distributors for a brand, save the ones you want, and order from them.

RUN YOUR REPRICER See which products have problems — no cost, price war, stuck at the floor, inactive listing. Build a pricing strategy in plain language, assign it, set minimum and maximum prices, and switch repricing on or off. Read your Buy Box win rate and recent price changes.

KEEP COSTS CURRENT Find SKUs with no cost and set them, so your profit figures and your cost-based price floors are right.

ANALYSE A BRAND Check a brand's revenue, seller count, competition and resale potential before you commit.

Requires a Seller Assistant account. Connect your Amazon seller account to unlock restriction checks and repricing.

Список инструментов сервера (15)

Технические названия из tools/list. Нужны только разработчикам.

get_account_context	Confirm that Seller Assistant is connected and return the authenticated user, current team, active plan, connected Amazon marketplaces, and remaining feature quotas. This tool requires no arguments, has no side effects, and should be used when the user asks whether the connection works or which account is active.
list_price_lists	List the price lists the team has already analyzed, newest first. Use this whenever the user refers to an earlier analysis rather than a new one — "the list I uploaded last week", "my Webstaurantstore list", or simply "my price lists". Each row carries the list_id that get_price_list_leads takes, so an old analysis can be read again without re-uploading the file and spending another quota unit. leads_count is how many profitable products the analysis found. A list whose status is not Download or Failed is still processing; poll check_price_list_status with its list_id. Returns at most 50 rows.
start_price_list_analysis	Start analyzing a supplier price list to find profitable Amazon resale opportunities. When mapping a large source file, inspect only a few representative rows to confirm the required fields and mapping; do not validate or analyze every row yourself. Provide the mapped items — each needs at least an "identifier" (UPC, EAN, or ASIN) and "cog" (cost of goods); "title", "supplier_sku" and "supplier_case_quantity" are optional. Optional expenses can override the user's saved PLA logistics, prep, tax, VAT, Amazon-fee, and miscellaneous-cost settings for this analysis only. For VAT-based non-US marketplaces, use vat_scheme, the applicable VAT rate, cog_incl_vat, and vat_on_seller_scheme/vat_on_seller_fees. Analysis runs in the background and can take several minutes. After this tool succeeds, automatically poll check_price_list_status about every 20 seconds, show progress when it changes, and call get_price_list_leads when processing finishes.
check_price_list_status	Check the processing status of a price list selected by list_id, exact description, or latest. Duplicate descriptions resolve to the newest matching list; with no selector, the newest team list is used. Processing can take several minutes for large lists — poll this periodically until status is no longer "Processing" (e.g. it becomes "Done", "Failed" or "Limit Reached") before calling get_price_list_leads.
get_price_list_leads	Get products from a completed price list selected by list_id, exact description, or latest. Duplicate descriptions resolve to the newest matching list; with no selector, the newest team list is used. result_set defaults to potential_leads, which returns only items meeting Seller Assistant's default criteria (minimum profit and ROI, minimum estimated monthly sales except in the local environment, Amazon not currently in the Buy Box, and excluding AI-sourced matches). Use custom with filters to find better or different opportunities using the same advanced filters as the PLA dashboard. Custom requests must contain at least one filter or a search term; the complete dataset is not returned to the agent and remains available through price_list_url. Range filters use keys such as {"greater_equal":20,"less_equal":100}; text filters use {"checkboxes":["contains"],"inputs":{"contains":"value"}}; brand/category/size_type use {"checkboxes":["is"],"inputs":{"is":["value"]}}; and warning, restrictions, source, preference, return_rate, out_of_stock, alert, and tags use the dashboard's include/exclude values. Call check_price_list_status first to make sure the list has finished processing. Use the returned identifier/supplier_sku and cog to create purchase orders for some or all of these leads afterwards. When presenting results, always show the ASIN and make it a clickable Markdown link using amazon_url, for example: Product: Title — ASIN: [B012345678](amazon_url). Also show price_list_url as a link to the full analysis. If count is greater than zero, ask the user whether they want to create a purchase order from some or all of the returned leads. Number the displayed leads so the user can select them by number; also accept selection by ASIN, supplier SKU, or product name, with an optional quantity for each.
create_purchase_order	Create or update a draft purchase order using exactly one source: (1) selected PLA leads via pla_items, or every current lead from price_list_id via use_all_leads; (2) ASINs, UPCs, EANs, identifiers, or supplier SKUs via lookup_items, searched in price_list_id when provided or in the current team's newest matching PLA items otherwise; or (3) direct items with unit_cost and at least one product identifier. Identify the supplier with supplier_id, supplier_name, or supplier_website. Ask the user for any one of these if the supplier is not known, and confirm the selected products and quantities before creating the order. When the user attaches a PDF, Excel, or CSV order file, extract all order rows because order files are expected to be small, map them to direct items or lookup_items, show the extracted supplier/items/costs/quantities for confirmation, and call this tool only after the user confirms. After creation, show purchase_order_url as a clickable link so the user can open, review, edit, export, or send the draft order.
find_purchase_orders	Find purchase orders belonging to the current team. Filter by supplier ID or partial supplier name, exact po_id, and/or status. Filters are combined. With no filters, return the 10 newest team orders. Always show purchase_order_url as a clickable link when presenting an order. Use page and limit only when the user needs more filtered results; do not retrieve every page automatically.
edit_purchase_order	Edit a team purchase order selected by order_id or exact po_id. This is a mutating tool: always show the proposed order fields and item additions, changes, or removals and obtain explicit user confirmation before calling it. For an attached supplier PDF, Excel, or CSV, read every row and map it to replacement_items, show a concise full-file summary including totals, and call with replace_all_items=true only after confirmation. Manual changes can update or remove lines by item_id or an exact ASIN, UPC, EAN, identifier, or supplier SKU in match_value. Never infer omitted supplier-file rows or silently remove lines.
match_product_identifiers	Manually match one or more Amazon ASINs to global product identifiers (12-digit UPC or 13-digit EAN) for the authenticated team. This uses Seller Assistant's existing product-matching rules: the ASIN identifies or creates the internal product for the selected marketplace, the UPC/EAN is linked as a manual global identifier, and an exact blacklist entry for the pair is removed. Before calling, show every ASIN → UPC/EAN pair and marketplace to the user and ask for confirmation.
get_product	Research one Amazon product by ASIN. This is the tool to use when a user asks about a product, whether it is worth selling, how well it sells, what it costs in fees, or who competes on it. It returns the title, brand, sales rank, estimated monthly sales, category, Buy Box and FBA/FBM prices, Amazon fees, offer and competitor counts, package size and weight, and warning flags such as meltable, fragile, oversize, hazardous or adult. Add cost_of_goods to also get the profit, ROI and margin at the current Buy Box price. Leave include_price_history true to also get the 30, 90, 180 and 365-day averages for price, sales rank, offer count and reviews, which show whether the product is stable or falling. For the team's own selling permission on the ASIN, use check_product_restriction.
check_product_restriction	Check whether the current team may sell one ASIN on Amazon. The answer comes back immediately. Use this for a single product. For more than one ASIN use start_restriction_check, which runs a batch in the background. The team needs a connected Amazon seller account for the marketplace region. The status is one of ALLOWED_TO_SELL, APPROVAL_REQUIRED or NOT_ELIGIBLE. Tell the user that an ASIN Amazon does not recognize also reports ALLOWED_TO_SELL, so a positive answer for an unusual ASIN is worth confirming in Seller Central.
list_restriction_checks	List the bulk restriction checks the team has already run, newest first. Use this when the user refers to an earlier check rather than asking for a new one — "the restrictions I checked yesterday", or "my restriction checks". Each row carries the restriction_id that check_restriction_status and get_restriction_check_results take, so a finished check can be read again without re-running it and spending restriction quota. The counts summarize the outcome: how many ASINs the team may sell, how many need approval, how many are not eligible, and how many failed. A row where is_terminal is false is still running. Returns at most 50 rows.
start_restriction_check	Start an asynchronous Amazon selling-restriction check. An active Amazon seller account connection for the marketplace region is required. Provide exactly one source: either a batch of ASINs plus marketplace_id, or price_list_item_ids previously returned by get_price_list_leads. For PLA items, the marketplace and ASINs are resolved automatically and all items must be from the same marketplace. After starting, poll check_restriction_status until terminal, then call get_restriction_check_results. If the user is referring to a check they already ran, use list_restriction_checks instead of starting a new one.
check_restriction_status	Lightweight status check for an asynchronous restriction batch. Poll this after start_restriction_check. Report progress only when it changes. When is_complete is true, call get_restriction_check_results. Stop polling whenever is_terminal is true.
get_restriction_check_results	Get paginated per-ASIN results for a completed restriction check. Each result is ALLOWED_TO_SELL, APPROVAL_REQUIRED, NOT_ELIGIBLE, or ERROR. Call check_restriction_status first. Use page and limit for large batches; never request or present more pages unless the user needs them.