Helium 10

Helium 10 Listing Builder — extract structured product attributes (product_name, brand_name, category, description, key_features, brand_voice, target_audience) from 1-5 product images via a multimodal LLM. Step 2 of the flow (after retrieve_listing_by_asin, before find_keywords_with_multi_source). Live multimodal call, non-idempotent (re-running the same images may vary the attributes). For LOCAL files the user uploads, do NOT base64 them — first get image_refs via request_image_upload_url (ask the user how many files and which type), then pass them here; see the image_refs / image_urls parameter docs. Precondition: you MUST call show_workflow_for_listing_builder FIRST if it has not been shown this session; do not start the flow from this tool. Not for: a hand-written product_info dict ready for generate_listing (skip this); pure OCR / screenshot text extraction (use a generic vision tool — this one is purpose-built for ecommerce attribute extraction). Output: `analyzed_product` (structured attributes) + `request_id` — store the request_id and pass it as parent_request_id to generate_listing. MANDATORY after this returns (do NOT skip, do NOT auto-advance to find_keywords_with_multi_source): 1. Show the user the analyzed product attributes (product_name, brand_name, category, description, key_features, brand_voice, target_audience) and let them correct / confirm it; merge corrections into product_info. 2. Ask whether to reference a competitor ASIN's writing style → if yes collect exactly ONE `brand_asin`. 3. Ask whether to include Amazon Alexa for Shopping Q&A content (formerly Rufus) → if yes collect up to 2 `rufus_asins`. Only after the attributes are confirmed AND both questions are answered, begin keyword collection (find_keywords_with_multi_source); do NOT re-ask brand_asin / rufus_asins inside generate_listing.

analyze_product_images

Helium 10 Available Ad Platforms (Data Query, step 1 of 5). Returns the advertising platforms available to query in your account (e.g. amazon, walmart). No inputs required — platforms are derived from your account credentials (the inbound bearer token). The entry point: use it to get valid platform keys before steps 2–5. Not for: actual performance numbers (use execute_ads_query after the intermediate steps). Next: get_ads_query_list(platform). ### Data Query pipeline ① get_ads_query_platforms → ② get_ads_query_list → ③ get_ads_query_schema → ④ get_ads_query_materials → ⑤ user selects specific profile(s) → ⑥ execute_ads_query ### Required profile selection Before calling execute_ads_query, the user must choose specific profiles from the profile/material results. 1. Call get_ads_query_materials for the relevant scope (profile, advertiser, vendor_account, or seller_account). 2. Build a concise selection list from the returned materials. Each option should include the display name plus the id that will be sent to execute_ads_query. 3. Use Cursor's AskQuestion tool with multi-select enabled when available so the user gets a real choice list. Do not proceed from a plain text assumption. 4. Continue only after the user selects at least one option. Send only the selected ids in profile_ids or the matching scope id field. 5. Never call execute_ads_query with all profiles by default, a guessed default profile, or profiles inferred only from prior context. If the returned material list is too large, show the most relevant profiles first and include an 'Other profile id' option. If there is only one returned profile, still ask the user to confirm that profile before executing.

get_ads_query_platforms

Helium 10 helper — discovers and disambiguates a Brand-Registered Amazon seller × marketplace pair before an SQA call. Lists the caller's linked Brand-Registered sellers (non-Brand-Registered links are filtered out here, so downstream never sees them); each row is one seller_id with store_name and a marketplaces[] list (one card may span a region, e.g. NA = US/CA/MX). Drive it as a two-step picker: pick a row to lock seller_id, then pick one value from that row's marketplaces[] to lock marketplace, and pass both to get_search_query_performance. Use when the user references 'my store / my account / this listing' without naming a pair, or when one seller spans multiple marketplaces. Not for: a pair already provided or locked this session (skip it); adding/editing seller links (Helium 10 account settings); seller-level sales/fee/inventory analytics.

get_brand_seller_profiles

Helium 10 Campaign Management Action Schema (Campaign Mgmt, step 2 of 3). Given a platform key and an action type, returns the JSON Schema needed to execute that specific action on a given platform.Use to learn what the request_body of an action must contain before calling execute_ads_campaign_mgmt_actions. Prerequisite: get_ads_campaign_mgmt_platforms (for valid platform + actionType pairs). Next: resolve profileId via get_ads_query_materials, then execute_ads_campaign_mgmt_actions.

get_ads_campaign_mgmt_schema

Helium 10 Campaign Management Platforms (Campaign Mgmt, step 1 of 3). Lists the advertising platforms available for ad management (e.g. amazon, walmart) and, for each, the supported action types (campaign_create, keyword_update, ...). The entry point: use it to discover valid platform keys and action types before steps 2–3. Next: get_ads_campaign_mgmt_schema(platform, actionType). ### Campaign Management pipeline ① get_ads_campaign_mgmt_platforms → ② get_ads_campaign_mgmt_schema → ③ resolve profileId via get_ads_query_materials → ④ execute_ads_campaign_mgmt_actions. Note: there is no dedicated materials tool in this pipeline — resolve the profileId (or advertiser / vendor_account / seller_account id, per the platform) with the Data Query tool get_ads_query_materials before calling execute_ads_campaign_mgmt_actions.

get_ads_campaign_mgmt_platforms

Helium 10 Keyword Research (Cerebro). Multi-ASIN keyword comparison for one main ASIN vs 1–10 competitors: returns the compare scope (union of organic phrases from the main ASIN and each competitor — not intersection only) with each phrase's CPS, search volume, main organic rank, competitor coverage, and competitive average rank; the scope includes main-only keywords (cps = 0), gap/opportunity keywords, and shared competitive keywords. When to use: call when the user's question — across multiple ASINs — involves keyword competition, shared keywords, competitor organic ranking, competitive pressure, CPS, or gap/opportunity keywords, even if they never say "CPS". Complement with get_keywords_by_asin as needed for richer per-ASIN metrics. Not for: single-ASIN questions with no compare intent. Edge case: the main ASIN may return no Cerebro rows — still call; results are then driven by the competitor side (rows where the main ASIN does not rank organically omit main_organic_rank).

compare_asin_keywords

Helium 10 Competitor Benchmark. For an ASIN group (main + up to 10 competitors), returns competitive benchmark data across 6 metrics — sales, revenue, price, BSR, review count, rating — for every ASIN in the session alongside two group averages: searched_products_avg (your session competitors) and top_competitors_avg (top 5 market performers, auto-resolved by LA). All ASINs returned in one call; the agent pairs each ASIN's values with the group averages to answer comparison questions. Omit competitor_asins to rely on top_competitors_avg only. Use for competitive health checks, pre-launch positioning, and finding the biggest performance gaps. Not for: full attribute comparison (use compare_listings); keyword-level analysis (use get_top_keywords).

get_competitor_overview

Helium 10 Competitor Keyword Rank Tracker. For a main ASIN with competitor ASINs configured in Keyword Tracker, returns the tracked keywords with your rank, each competitor's rank, relative_rank, rank_avg, and Competitor Performance Score (CPS) side-by-side. Use to find rank gaps on shared keywords, prioritize which keywords deserve PPC or listing investment, and monitor whether competitor moves are eroding your visibility. Not for: a single-ASIN view (use list_tracked_keywords); discovering new keywords (use get_keywords_new_suggestion); competitors not yet in Keyword Tracker (add them there first). Errors: invalid_input / invalid_asin / no_result / no_data / rate_limited / upstream_timeout. Degradation: reach_limitation (partial results returned).

list_tracked_competitor_keywords

Delete one or more configured Amazon COGS records by cogs_id (batch, max 100). Obtain ids from list_amazon_cogs first. Only rows owned by token-authorised sellers are deleted; foreign / unknown / already-deleted ids are silently ignored (deleted_count may be < ids sent — treat as success). Deleting a middle by_period segment leaves a gap on that SKU's timeline (expected). NOT for create/update (use edit_amazon_cogs, which does not use cogs_id) or browsing (use list_amazon_cogs).

delete_amazon_cogs

Helium 10 Product Research (formerly Black Box — Products, inactive view). Discovers Amazon listings that are now inactive/discontinued/dropped but were active and tracked within the last 360 days, by filters (category, last-active-date, historical sales/revenue, reviews, price, brand, fulfillment). Returns last known price, 360-day historical sales & revenue, review count, and rating. Use for market-gap mining, vacated-niche discovery, dropped-competitor post-mortems, and replication-candidate research. Not for: active listings (use search_products); keyword research (use search_amazon_keywords). If the user asks for historical Price for returned inactive products, call get_asin_price_history once per selected ASIN.

search_inactive_products

Runs an already-existing tool (e.g. get_keywords_by_asin, get_keywords_by_keyword) exactly as if it were called directly, but returns a download link to the result instead of the data itself. Default to calling the underlying tool directly (get_keywords_by_asin, get_keywords_by_keyword, etc.) in all cases. Only use download_tool_result when the user explicitly asks for it by name — never infer this tool just because the user wants a file, export, or link in general terms, and never call it proactively as a shortcut for a large response. params: pass exactly what you'd send directly to whichever tool tool_name names — same fields, same types.

download_tool_result

Warning: This tool can overwrite or remove existing COGS history. Overlay updates may trim or split overlapping records, while persistent updates may clear and replace prior period records. Create or update Amazon COGS via interval overlay upsert (batch, max 100 items). Each item identifies a SKU by seller_id + marketplace (short country code) + sku and sets cogs_type, cost components, and (for by_period) an effective date interval. Describe the DESIRED new interval and costs, not 'edit row N': this is a cover-and-replace overlay, NOT row-ID targeting — there is no cogs_id on input (any cogs_id/asin/currency/total_cogs passed is ignored; currency follows marketplace; shipping_cost/tariffs omit/null → 0). New intervals overlay existing ones: overlapping history is trimmed/split, non-overlapping history preserved; writing persistent clears prior by_period rows for that SKU. Transaction is all-or-nothing. Use to set/update per-SKU unit costs before trusting net profit. NOT for reading (use list_amazon_cogs) or deleting (use delete_amazon_cogs, which deletes by cogs_id). After success call list_amazon_cogs to see the resulting timeline (overlay may split/rewrite rows into new ids). Do not mix persistent and by_period for the same SKU in one batch; by_period items for the same SKU must not overlap each other.

edit_amazon_cogs

Helium 10 Execute Campaign Management Actions (Campaign Mgmt, step 3 of 3, terminal, WRITE). Submits one or more ad-management actions (create / update / delete campaigns, ad groups, keywords, ...) to Helium 10 for a single platform + profileId. ### Confirmation is REQUIRED before calling This tool mutates live advertising state. BEFORE invoking it, you MUST present the exact platform, profileId, and the full list of actions to the user and get explicit confirmation via an AskUserQuestion-style prompt. Do not call it on inferred intent, and never batch-confirm — the user must see each action. Deletes are irreversible. ### profileId (required) profileId is mandatory. Resolve it with the Data Query tool get_ads_query_materials (materialType/level=profile). There is no materials tool in this pipeline. ### Hierarchical creation (Campaign → Ad Group → Product / Keyword) Campaigns contain Ad Groups; Ad Groups contain Products and Keywords. When a creation response returns an id-name mapping, use those ids directly as parent references for the next-level creation — do not re-resolve them. ### Limits maxActionsPerRequest (from get_ads_campaign_mgmt_platforms) caps the number of actions per call; split larger batches across calls. Prerequisites: get_ads_campaign_mgmt_platforms (valid platform + actionType), get_ads_campaign_mgmt_schema (request_body shape per action), get_ads_query_materials (profileId).

execute_ads_campaign_mgmt_actions

Helium 10 Listing Builder — build a Keyword Bank by fetching keywords from one or more Helium 10 sources for the main ASIN and/or its competitors, returning a merged, deduplicated, ranked list (up to 150) ready for generate_listing / rewrite_listing_section. Step 3 of the flow (after analyze_product_images, before generate_listing). The main ASIN and competitor_asins are each optional — provide at least one; supplying both is strongly recommended for the best coverage. This is the ONLY supported way to build a Keyword Bank for LB — keywords from other tools lack the fields LB needs for internal tiering and will cause downstream errors; do NOT substitute them. Live multi-source fetch; the `filters` argument is accepted but IGNORED in this release (server applies per-source defaults). Precondition: you MUST call show_workflow_for_listing_builder FIRST if it has not been shown this session; do not start the flow from this tool. Not for: standalone keyword research (use get_keywords_by_asin / get_keywords_by_keyword / search_amazon_keywords — their output is NOT compatible with generate_listing). BEFORE CALLING, let the user choose sources: present these 7 Helium 10 keyword sources (as a short list or table) and ask which to use (multi-select); if the user has no preference, default to aba_converting_keywords + top_keywords: 1. `aba_converting_keywords` (default): ABA Converting Keywords — Amazon Brand Analytics terms that convert to sales in this niche. ⚠️ PRECONDITION: only returns data when the user's Amazon store is connected/bound in Helium 10 — otherwise this source returns NO keywords. Flag this to the user before they select it. 2. `sqp_sales_keywords`: SQP Sales Keywords — Search Query Performance terms driving the most purchases for the ASIN. ⚠️ PRECONDITION: only returns data when the user's Amazon store is connected/bound in Helium 10 AND at least one of the main ASIN / competitor ASINs belongs to that connected store — otherwise this source returns NO keywords. Flag this to the user before they select it. 3. `top_keywords` (default): Top Keywords — the highest-traffic keywords the ASIN and its competitors already rank for. 4. `opportunity_keywords`: Opportunity Keywords — high-traffic terms where the ASIN ranks weakly (ranking gaps to capture). 5. `historical_top_keywords`: Historical Top Keywords — top keywords aggregated over a longer historical window. 6. `top_performing_organic_keywords`: Top Performing Organic Keywords — the best organic-rank keywords for the ASIN / competitors. 7. `top_performing_sponsored_keywords`: Top Performing Sponsored Keywords — the best-performing sponsored (PPC) keywords. Whenever `aba_converting_keywords` or `sqp_sales_keywords` is offered or selected, PROMINENTLY surface its ⚠️ precondition (in the source guide above) to the user: both return NOTHING unless the user's Amazon store is connected/bound in Helium 10 (and `sqp_sales_keywords` additionally requires at least one of the main ASIN / competitor ASINs to belong to that store). If, after the call, either source contributed zero keywords, remind the user of this precondition as the likely cause. AFTER IT RETURNS, render two tables to the user: 1. Keyword Bank TABLE — one row per keyword, sorted by priority_score DESCENDING; columns # | Keyword | Search Volume | CPS | Priority Score | Sources (you may add Competing Products / Cerebro IQ Score). Leave null / missing cells blank; format the CPS column as `X/10` (cps is a 0-10 number; max 10, 1 decimal, drop a trailing .0 — e.g. 4.8 -> '4.8/10', 4.0 -> '4/10'). 2. SUGGESTED slot-allocation PREVIEW table (Slot | Keywords): Allocate keywords ONLY from the Keyword Bank to slots by priority_score HIGH→LOW, in slot order TITLE → each BULLET → DESCRIPTION (bullets outrank description for the higher-priority keywords). Default 3, max 6 keywords per slot; default 5 bullets (5-10 allowed). TITLE and DESCRIPTION need NOT be semantically related — just take the next-highest priority_score keywords. For EACH BULLET, pick the highest-priority unallocated keyword as the bullet's theme, then group ~3 of its closest-meaning keywords so one bullet highlights ONE product feature. Mark it a PREVIEW — the user approves the final per-slot allocation in generate_listing.

find_keywords_with_multi_source

Helium 10 Listing Builder — AI-generate a complete Amazon listing (title + item_highlight + 5-10 bullets + description) from a user-approved keyword allocation. Step 4 of the flow (after find_keywords_with_multi_source, before rewrite_listing_section). Live LLM call, non-idempotent; output language is derived server-side from `marketplace` (e.g. JP → Japanese, DE → German). Prerequisites: the Keyword Bank from find_keywords_with_multi_source, the user-confirmed analyzed attributes from analyze_product_images, brand_asin & Alexa for Shopping Q&A reference ASINs (legacy parameter name: `rufus_asins`) already asked, and a slot-by-slot-approved allocation table. Precondition: you MUST call show_workflow_for_listing_builder FIRST if it has not been shown this session; do not start the flow from this tool. Not for: refining just one section of an already-generated listing (use rewrite_listing_section); speculative calls without the approved allocation. MANDATORY before calling (do NOT skip, do NOT call speculatively): 1. Use the Keyword Bank returned by find_keywords_with_multi_source. Do NOT re-collect keywords from other tools — keywords from outside find_keywords_with_multi_source lack the fields required for tiering. 2. Allocate keywords ONLY from the Keyword Bank to slots by priority_score HIGH→LOW, in slot order TITLE → each BULLET → DESCRIPTION (bullets outrank description for the higher-priority keywords). Default 3, max 6 keywords per slot; default 5 bullets (5-10 allowed). TITLE and DESCRIPTION need NOT be semantically related — just take the next-highest priority_score keywords. For EACH BULLET, pick the highest-priority unallocated keyword as the bullet's theme, then group ~3 of its closest-meaning keywords so one bullet highlights ONE product feature. 3. Present the FULL allocation table to the user and get slot-by-slot approval; the user may remove / add / swap / reset keywords per slot — re-show the table after every edit. 4. Call this tool only AFTER the user explicitly approves the allocation. Returns: `request_id` (show it to the user for recall via get_generated_listing_data) and the generated title / bullet_points / description / item_highlight (Amazon's Item Highlight, generated together with the title — render it alongside the title, not as a bullet). Amazon now splits the legacy single <=200-character title into TWO fields: `title` (concise, <=75 characters) and `item_highlight` (<=125 characters). A short ~75-character title is CORRECT and compliant - do NOT lengthen it, keyword-stuff it, or treat it as incomplete; extra selling points and keywords belong in item_highlight. The two fields together replace the old long title. After it returns, render the listing with each allocated keyword bolded where it appears in its slot and a "Missing keywords" line per slot — see show_workflow_for_listing_builder for the exact rendering rules.

generate_listing

Helium 10 Alerts — current Buy Box standing across a seller's monitored ASINs. Omit marketplace for an all-marketplaces overview (winning/losing counts and win rate per marketplace); pass marketplace for single-market detail including the specific losing ASINs, their current Buy Box winner, and ASINs lost in the last 7 days. ASINs with no Buy Box winner data at all (neutral — not yet synced or no competing offers) are excluded from every losing_count, but still count toward win_rate's total-monitored denominator. For one ASIN's Buy Box history over time use search_buybox_history.

get_buybox_summary

Helium 10 Alerts — account-level rollup of what changed in the last 24h or 7d for a seller in one marketplace. Aggregates alert events (plus Seller Feedback notifications) by urgency (P0–P3), by event type, and by ASIN, and returns the P0 critical events that need immediate action. Use to answer 'what changed today / this week?' and 'what's most urgent?'. For raw per-event detail use search_alert_events.

get_change_rollup

Return FBA inventory health metrics per product row: days of supply (a decimal number of days, e.g. 12.75 — report it as-is, do not present it as a whole number) and inventory age bucket unit counts (<31 days, 31-180 days, >180 days). Each row includes standard product information (without fulfillment_type — implicit FBA). Not on-hand/inbound quantity counts; not FBM; not a time series. The unit counts here are health signals only — use them to judge aging/slow-moving risk, never as an authoritative quantity source. Do NOT compare or reconcile them with get_inventory_values; the two use different methodologies and are not expected to match. Use when the user asks about FBA stock health, days of supply, slow-moving or aged inventory in Amazon fulfillment centers, or restock risk from an FBA aging perspective. Not for: quantity snapshots (available, inbound, unfulfillable) or FBM (use get_inventory_values); sales velocity over time (use get_sales_velocity); profit & loss or fees (use Phase 1 P&L tools). Combine seller_ids, marketplace, asins, skus, and pagination to limit payload size. Do not pass fulfillment_type — this tool does not accept it. Pass days_of_supply_min / days_of_supply_max to filter by supply days server-side (inclusive bounds); rows with null days_of_supply are omitted when a range filter is active — do not assume they were evaluated as zero. Pass inv_age_stage (less_31_days | 31_to_180_days | over_180_days) to find SKUs that HAVE units in that age bucket: this is a presence filter, so returned rows still show all three inv_age_* counts and a SKU with over-180-day stock may also have younger inventory. Combine inv_age_stage with days_of_supply_max for restock / long-term-storage triage.

get_fba_inventory_health_status

Helium 10 Listing Builder — fetch a previously generated or rewritten record (analyze-image, generate-listing, or rewrite-section) by its request_id, to restore baseline state across sessions. Standalone helper (not a numbered step); read-only and idempotent, reads persisted records (same user, same scope). Use it when the user references a listing from an earlier session, or to reload the baseline (title / item_highlight / bullets / description) before rewrite_listing_section. Not for: starting a brand-new listing (use generate_listing); live Amazon catalog data (use retrieve_listing_by_asin); cases with no known request_id (guide the user to look it up in their prior session). The `payload` field of the response is polymorphic, depending on `generation_type`: 0 (GENERATE LISTING) -> {listing (title, bullet_points, description, item_highlight), all_keywords:[{phrase, search_volume, cps, starred, suggested, priority_score, keyword_sources}]} (all_keywords is the snapshot the caller passed into generate_listing; null for records written before that field was persisted); 1 (REWRITE TITLE) -> {target, rewritten_content, original_content, rewritten_item_highlight, original_item_highlight} (title and item_highlight are rewritten together in one call); 2/3 (REWRITE BULLET/DESCRIPTION) -> {target, rewritten_content, original_content} (rewritten_item_highlight / original_item_highlight are always null for these targets); 4 (ANALYZE IMAGE) -> AnalyzedProduct fields; 5 (GENERATE BRAND VOICE) -> reserved, not produced by the current tools.

get_generated_listing_data

Return current Amazon inventory quantity metrics per product row, with fulfillment_type (FBA or FBM) on each row. FBA rows include available, inbound pipeline quantities, and unfulfillable. FBM rows include available only (FBA-only keys are omitted, not zero-filled). Not a time series; not inventory age or days-of-supply. This is the authoritative source for inventory quantities; do NOT reconcile or cross-check these counts against get_fba_inventory_health_status, whose numbers are health signals only and follow a different methodology. Use when the user asks how much stock is on hand, in transit to Amazon (inbound), or unfulfillable; needs SKU/ASIN-level inventory counts across sellers/marketplaces; restock or fulfillment planning based on quantity snapshots. Not for: FBA health/aging/days of supply (use get_fba_inventory_health_status); sales velocity or units sold over time (use get_sales_velocity); profit & loss or fees (use Phase 1 P&L tools). Pass seller_ids, marketplace, asins, skus, and/or fulfillment_type (FBA | FBM) to limit rows; omit fulfillment_type for both channels. Use pagination when listing many SKUs. Pass available_min / available_max to filter rows by on-hand quantity (inclusive bounds on inventory.available) without post-processing in agent context. Combine sort_by=available with a small page_size to retrieve top/bottom N SKUs by stock level in one call: sort_order=asc surfaces lowest-stock SKUs first (restock prioritization), sort_order=desc surfaces highest-stock SKUs first.

get_inventory_values

Helium 10 Keyword Research (formerly Cerebro). Reverse keyword search for one Amazon ASIN: returns every phrase where the ASIN is visible on Amazon — organic, sponsored, or in Amazon's recommendations — with search volume, rank, CPC, ABA top-3 click/conversion share, and H10 metrics (CPR, IQ score, title density). Use for keyword discovery from your own listing, competitor reverse-search, listing coverage audits, and PPC keyword selection. Not for: seed-keyword expansion with no ASIN (use get_keywords_by_keyword); scoring a finalized list (use analyze_keywords). Pass optional time_period (YYYY-MM) to look back at a single past month (e.g. last November's related keywords); omit for current data. One month per request; query each month separately for multi-month comparisons.

get_keywords_by_asin

Helium 10 Keyword Research (formerly Magnet). Seed-keyword expansion for one keyword: returns related long-tail and derivative phrases with search volume, relationship type, CPC, ABA top-3 click/conversion share, and H10 metrics (CPR, IQ score, title density). Use for keyword planning from a single concept, PPC keyword selection, listing keyword coverage, and hero-keyword discovery. Not for: reverse search on an ASIN (use get_keywords_by_asin); scoring a finalized list (use analyze_keywords). Pass optional time_period (YYYY-MM) to look back at a single past month (e.g. last November's related keywords); omit for current data. One month per request; query each month separately for multi-month comparisons.

get_keywords_by_keyword

Helium 10 Alerts — a seller's monitoring status. Omit asin for an account overview: total/used/available monitoring slots and the list of monitored ASINs (asins[]) with their marketplace, seller SKU and monitoring start date. Pass asin to get asin_rows[] — one row per marketplace the ASIN appears in, each with is_monitored, marketplace and seller SKU. Essential for distinguishing 'no changes' from 'not monitored' when other Alerts tools return empty.

get_monitoring_status

What: Return the caller's bound Amazon seller accounts (one row per SP-API token / seller binding). Each row includes seller_id, marketplace_list (short country codes), region (NA / EU / FE), status (whether the binding is still valid), optional alias, and created_at (UTC bind time). No required input — default returns all bindings (active and inactive). Optional status filter narrows to valid-only or invalid-only. When to use: User (or agent) needs to know which seller IDs and marketplaces are available for this account before calling other Commerce tools; wants to list / audit linked Amazon seller accounts; needs to distinguish active vs revoked / invalid tokens; wants a human-readable alias when present. When NOT to use: Brand Registry / SQA seller × marketplace picker → get_brand_seller_profiles (ResearchMCP). Use that tool when the next call is Brand-Registry–gated (e.g. get_search_query_performance, ABA Brand Analytics), or the user only needs a Brand-Registered seller_id + one marketplace from marketplaces[]. It filters out non–Brand-Registered and does not return region / status / alias / created_at, and its marketplace enum is narrower (US/UK/DE/JP/CA/FR/IT/ES). Do not use this Commerce tool as a substitute for that picker, and do not use get_brand_seller_profiles when you need the full SP-API binding roster for P&L / inventory / COGS / Indirect Costs. Product catalog / SKU browse → list_my_products (HP-1267) P&L, inventory, COGS, or Indirect Costs metrics / CRUD → the dedicated tools for those domains Discovering Amazon sellers that are not linked to this H10 account Guidance: Call with no arguments first to discover the full set of seller_id + marketplace_list values, then pass those into downstream Commerce tools' seller_ids / marketplace filters. Prefer status=true when the user only wants currently usable sellers. Do not invent seller IDs or marketplaces. If the task is specifically SQA / Brand Analytics and Brand Registry eligibility matters, prefer get_brand_seller_profiles instead.

get_my_amazon_seller_accounts

Helium 10 Alerts — current attribute snapshot for one ASIN: price, FBA fee, Buy Box owner, number of sellers, listing status (active/suppressed/inactive), is_adult_flagged, category, brand, main image, package dimensions (size_tier) and last-updated time. Answers 'what is it now?' (current state), as opposed to search_alert_events ('what changed'). The ASIN must have monitoring enabled; querying an unmonitored ASIN returns an INVALID_INPUT error.

get_product_live_status

Return units sold over time (sales velocity) per product row, bucketed by day / week / month over an inclusive date range. Each row includes product information (including fulfillment_type). Not a single snapshot; not revenue, fees, or other P&L metrics. Use when the user asks how units sold trend, compare periods, velocity by SKU/ASIN, or needs time-bucketed unit counts for inventory / restock planning. Not for: snapshot on-hand / inbound quantities (use get_inventory_values); FBA health / aging (use get_fba_inventory_health_status); full P&L trends (use get_product_profit_and_loss_summary_series or get_account_profit_and_loss_summary_series). Requires granularity + date range. Narrow with seller_ids, marketplace, asins, skus, fulfillment_type, and pagination. Prefer this over product P&L series when only units sold matter (smaller payload).

get_sales_velocity

Helium 10 Alerts — seller feedback rating and recent negative reviews, for reputation monitoring and competitor assessment. seller_id may be the caller's own seller or a competitor's. For an account-level rollup that also surfaces feedback notifications alongside other alert types, see get_change_rollup.

get_seller_feedback

Helium 10 Alerts — FBA Size Tier optimization suggestions for a seller's monitored ASINs: which products could drop to a cheaper Size Tier by adjusting packaging dimensions, and the estimated FBA fee savings. Omit asin for all monitored products in the marketplace; pass asin for a single product. Returns an empty suggestions list when no optimization applies. For a one-off historical event of when this suggestion appeared, see search_alert_events (alert type SIZE_TIER_OPTIMISATION).

get_size_tier_suggestions

Helium 10 Keyword Research (formerly Cerebro). Batch enrichment for an explicit list of 1–200 keywords: one row per keyword with search volume, CPC, ABA top-3 click/conversion share, and H10 metrics (CPR, IQ score, title density, competing products). Use when the user already has a candidate-keyword set to score, rank, structure into ad groups, or cross-compare. Not for: deriving new terms from one seed (use get_keywords_by_keyword); reverse search on an ASIN (use get_keywords_by_asin). Note: output order does NOT match input order — match results by the phrase field.

analyze_keywords

Helium 10 Keyword Database Search (formerly Black Box — Search Keywords). Searches the FULL Helium 10 keyword database (not one ASIN's keywords) by filters (search-volume / impression range, word count, competing products, price, monthly revenue, reviews, rating, category, density, broad reach potential, and top-10 competitor distribution buckets). Returns paginated keyword rows with demand metrics, competitive landscape, and aggregated top-10 competitor profile data. Use for market-level keyword discovery, low-competition keyword mining, niche sizing by demand, and category keyword-landscape analysis — no ASIN or seed term needed. Not for: ABA click/conversion share & top clicked products (use search_amazon_brand_analytics); product lists (use search_products / search_inactive_products). If the user asks for historical Search Volume for returned keywords, call get_keywords_search_volume_history once per selected phrase.

search_amazon_keywords

Helium 10 Keyword Tracker. Returns historical sponsored and organic rank trends for one keyword (fuzzy match) over a date range, scoped to an ASIN/product URL — summary metrics (top / lowest / average for both surfaces) plus full time-series rank history. Use to analyze rank movement over time, find peak ad-placement periods, detect organic-rank decline, and evaluate phased ranking performance. Not for: current snapshots across all tracked keywords (use list_tracked_keywords); discovering new keywords (use get_keywords_by_asin); batch metrics across a list (use analyze_keywords). Errors: invalid_input / invalid_asin / no_result / no_data / rate_limited / upstream_timeout. Degradation: reach_limitation (partial results returned).

get_keywords_rank_history

Helium 10 Keyword Tracker. Returns metrics for keywords ALREADY tracked in Keyword Tracker — by ASIN/product URL, or account-wide when the ASIN is omitted — with search volume + trend, organic & sponsored rank + trend, CPR, boost status, tags, and permission-gated keyword_sales and ABA shares. Use for monitoring rank movement, detecting rank drops/gains, assessing visibility after a PPC or listing change, and reviewing the full tracked set. Not for: untracked reverse search (use get_keywords_by_asin); discovering new keywords to add (use get_keywords_new_suggestion); competitor comparison (use list_tracked_competitor_keywords); rank history over time (use get_keywords_rank_history). Errors: invalid_input / invalid_asin / no_result / no_data / rate_limited / upstream_timeout. Degradation: reach_limitation (partial results returned).

list_tracked_keywords

Keywords search volume history (not a Black Box Web module). Returns weekly search-volume points for one keyword (keyword); each point is the trailing 30-day search volume for that week, and data updates about weekly. Default last 30 days when both dates omitted. Pass start_date and end_date together (both YYYY-MM-DD within the last 3 years), or omit both for the default last 30 days; do not pass only one date. Use when the user asks for search volume history or demand trend. Not for ASIN price/BSR/reviews, keyword ranking, batch multi-keyword, or keyword discovery rows (use search_amazon_keywords).

get_keywords_search_volume_history

Return a paginated list of CONFIGURED Amazon COGS records. One row = one COGS configuration (not one SKU); a SKU appears on multiple rows when cogs_type=by_period (non-overlapping effective periods). Each row has cogs_id (for delete), product identity (product_name, asin, sku, brand, image_url, product_page_url, seller_id, marketplace, fulfillment_type, sku_status) and COGS fields (cogs_type, currency, product_cost, shipping_cost, tariffs, total_cogs, starts_at, ends_at). No required input. Use to view / audit / search configured unit costs, or to get cogs_id before delete_amazon_cogs. NOT for actual COGS dollars in P&L (use get_product_profit_and_loss_*; cost_of_goods=0 there may mean COGS not configured). Only SKUs WITH configured COGS are returned. Narrow with seller_ids, marketplace (short country codes US/CA/...), asins, skus, fulfillment_type (FBA|FBM), cogs_type (by_period|persistent), sku_status (active|inactive), value range filters, or effective-date endpoint filters; sort with sort_by + sort_order. Values compared as stored (no FX conversion across marketplaces).

list_amazon_cogs

Return a paginated list of the caller's OWN Amazon product rows (one row per SKU x marketplace x seller). Each row carries product identity only: product_name, asin, sku, brand, image_url, product_page_url, seller_id, marketplace, fulfillment_type. No P&L, inventory, or listing-analysis metrics. No required input — default scope is all sellers authorised by the Pacvue token; call with no arguments to page through the full authorised catalog. Use when the user asks to list, browse, or find their own products/SKUs/ASINs across linked seller accounts, needs product metadata (title, image, Amazon listing URL) before calling P&L or inventory tools, or wants to resolve which SKUs match a name/brand within their catalog. Narrow with seller_ids, marketplace, asins, skus, fulfillment_type (FBA | FBM), product_name (case-insensitive LIKE on title), or brand_name (case-insensitive LIKE on brand). Not for: market-wide product or competitor research (use search_products / search_inactive_products); profit & loss metrics (use get_product_profit_and_loss_summary); inventory on-hand / inbound quantities (use get_inventory_values); deep single-ASIN listing profile / BSR / scores (use get_listing_details). Does not distinguish active vs inactive listing status; rows reflect whatever Profits has ingested. No sort parameters — order is backend-defined.

list_my_products

Helium 10 Listing Analyzer. For one Amazon ASIN, returns the complete listing profile: title, Listing Quality Score (LQS), age, image count, variation count, category & subcategory BSR, seller name & region, price, coupon status, parent- and ASIN-level sales with revenue estimates, review count, sales-to-review, shipping details, weight, storage fee, and top-10 keywords with search volumes. Use as the primary single-ASIN lookup for listing audits, pre-launch benchmarking, and competitive research on a specific product. Not for: comparing multiple ASINs (use compare_listings); the LQS pass/fail checklist (use get_listing_score); keyword strategy (use get_top_keywords); writing / generating / optimizing / rewriting listing copy — title, bullets, or description (that is the Listing Builder flow: start with show_workflow_for_listing_builder, not this tool).

get_listing_details

Helium 10 Listing Comparison. Returns the field set from Compare Key Metrics for every ASIN in the session — the main ASIN plus all competitor ASINs — as an array of objects under asins. The main ASIN is always first, flagged with is_main: true. Maps to the Compare Key Metrics Across ASINs table in the LA UI. Use to benchmark your listing against multiple competitors at once, see where you're ahead or behind on content and sales, and build a prioritized improvement list. Competitor ASINs that are valid 10-char codes but can't be resolved upstream are not returned as empty rows — they are split out into failed_asins as {asin, error} so the asins rows always carry real data. Not for: a single-ASIN lookup (use get_listing_details); keyword comparison (use get_top_keywords); the LQS checklist (use get_listing_score).

compare_listings

Helium 10 Listing Quality Audit. For an ASIN group (main + up to 10 competitors), returns the session-average LQS (0–10) with aggregate pass/fail counts per criterion, plus individual LQS scores and pass/fail results for all 13 criteria per ASIN — across Copy, Media, and Review (title symbols/length, ≥5 bullets, bullet length, image resolution & count, white-background main image, video presence, description ≥1000 chars or A+, ≥20 reviews, ≥4-star rating). All ASINs returned in one call; the agent surfaces whichever ASIN the user asks about. Use to understand content-compliance scores, pinpoint which elements drag LQS down, and compare listing quality across competitors. Not for: full attribute lookup (use get_listing_details); a quick LQS number alongside other metrics (use compare_listings).

get_listing_score

Returns the current caller's MCP tool-call remaining usage quota for the current period: the account id, the period limit, how many calls were used and how many remain. Calling this tool does not itself consume quota.

get_mcp_usage_info

Helium 10 New Keywords to Track. For a given ASIN, returns keywords NOT yet in your Keyword Tracker — drawn from the ASIN's own footprint and its tracked competitors' footprints — with search volume, keyword_sales, CPS, ABA shares, and a source field (main product vs a specific competitor). Use to expand your tracked set after a listing change, find high-potential terms you're missing, and for tracking hygiene. Candidates only — add them in the Helium 10 UI. Not for: already-tracked metrics (use list_tracked_keywords); reverse search with no tracking context (use get_keywords_by_asin); competitor comparison (use list_tracked_competitor_keywords). Errors: invalid_input / invalid_asin / no_result / no_data / rate_limited / upstream_timeout. Degradation: reach_limitation (partial results returned).

get_keywords_new_suggestion