SellerSprite MCP MCP integration for AI agents.
Connect AI agents to SellerSprite MCP through 47 structured actions, including competitor lookup, aba research monthly, and aba research trend. Review authen…
- ACTION CONTRACTS
- 47
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the SellerSprite MCP integration exposes
The SellerSprite MCP Agent App exposes 47 provider-backed actions for data and marketing work. Its current contract lets an authorized agent find competing amazon products by marketplace, category, brand, seller, asin, keyword, and product filters, research monthly amazon brand analytics keywords using rank, search, click, conversion, and market-pattern filters, and retrieve weekly or monthly amazon brand analytics trend data for one keyword. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected SellerSprite MCP account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SellerSprite MCP capabilities.
Showing 12 of 47 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
competitor_lookupREADFind competing Amazon products by marketplace, category, brand, seller, ASIN, keyword, and product filters.
INPUTS: marketplace / month / brand / sellerName / asins
aba_research_monthlyREVIEWResearch monthly Amazon Brand Analytics keywords using rank, search, click, conversion, and market-pattern filters.
INPUTS: marketplace / date / departments / excludeKeywords / includeKeywords
aba_research_trendREVIEWRetrieve weekly or monthly Amazon Brand Analytics trend data for one keyword.
INPUTS: marketplace / keyword / timeGranularity / returnFields
aba_research_weeklyREVIEWResearch weekly Amazon Brand Analytics keywords using rank, search, click, conversion, and market-pattern filters.
INPUTS: marketplace / date / departments / excludeKeywords / includeKeywords
asin_competitorREVIEWRetrieve competing products identified for one Amazon ASIN.
INPUTS: marketplace / asin / size / returnFields
asin_coupon_trendREVIEWRetrieve the historical coupon trend for one Amazon ASIN.
INPUTS: marketplace / asin / returnFields
asin_detailREVIEWRetrieve SellerSprite product, sales, ranking, price, review, and seller data for one Amazon ASIN.
INPUTS: marketplace / asin / returnFields
asin_detail_with_coupon_trendREVIEWRetrieve ASIN details together with the product's historical coupon trend.
INPUTS: marketplace / asin / returnFields
asin_predictionREVIEWRetrieve SellerSprite sales predictions for one Amazon ASIN.
INPUTS: marketplace / asin / returnFields
asin_sales_trendREVIEWRetrieve the historical sales trend for one Amazon ASIN.
INPUTS: marketplace / asin / returnFields
bsr_predictionREVIEWEstimate Amazon product sales from a Best Sellers Rank and top-level category.
INPUTS: marketplace / bsr / categoryId / returnFields
call_toolREVIEWCall a current SellerSprite MCP tool with JSON arguments after inspecting its live schema and behavior annotations with list_tools.
INPUTS: toolName / arguments
INPUT CONTRACTS
Know what the action needs before it runs.
competitor_lookup
marketplaceREQUIRED- The Amazon marketplace code supported by SellerSprite.
monthOPTIONAL- The historical month in YYYYMM format; omit when the tool supports latest data.
brandOPTIONAL- The brand value documented by SellerSprite for this MCP tool.
sellerNameOPTIONAL- The seller name value documented by SellerSprite for this MCP tool.
asinsOPTIONAL- Amazon ASINs to query, with at most 40 values.
aba_research_monthly
marketplaceREQUIRED- The Amazon marketplace code supported by SellerSprite.
dateOPTIONAL- The SellerSprite reporting period documented for this tool.
departmentsOPTIONAL- The departments value documented by SellerSprite for this MCP tool.
excludeKeywordsOPTIONAL- Keywords that results must exclude.
includeKeywordsOPTIONAL- Keywords that results must include.
aba_research_trend
marketplaceREQUIRED- The Amazon marketplace code supported by SellerSprite.
keywordREQUIRED- The Amazon search keyword.
timeGranularityOPTIONAL- The time granularity value documented by SellerSprite for this MCP tool.
returnFieldsOPTIONAL- Comma-separated response field names to reduce SellerSprite MCP result size and token usage.
aba_research_weekly
marketplaceREQUIRED- The Amazon marketplace code supported by SellerSprite.
dateOPTIONAL- The SellerSprite reporting period documented for this tool.
departmentsOPTIONAL- The departments value documented by SellerSprite for this MCP tool.
excludeKeywordsOPTIONAL- Keywords that results must exclude.
includeKeywordsOPTIONAL- Keywords that results must include.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Competitor Lookup
Find competing Amazon products by marketplace, category, brand, seller, ASIN, keyword, and product filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
competitor_lookupVerify with Aba Research Monthly
Research monthly Amazon Brand Analytics keywords using rank, search, click, conversion, and market-pattern filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
aba_research_monthlySAFETY BOUNDARY
Operate SellerSprite MCP with explicit limits
- Authorize SellerSprite MCP with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned SellerSprite MCP data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in SellerSprite MCP rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SellerSprite MCP task completed successfully.
CONNECTION MODEL
API key
SellerSprite MCP secret key from https://open.sellersprite.com/mcp.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 42
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by SellerSprite MCP.