SellerSpace MCP integration for AI agents.
Connect AI agents to SellerSpace through 9 structured actions, including get ad metric history, call tool, and discover fields. Review authentication, inputs…
- ACTION CONTRACTS
- 9
- 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 SellerSpace integration exposes
The SellerSpace Agent App exposes 9 provider-backed actions for productivity, data, and marketing work. Its current contract lets an authorized agent get time-series or placement-level metrics for one sellerspace advertising campaign, ad group, promoted product, keyword, target, or search term, call an explicitly approved sellerspace mcp read tool with json arguments after discovering its live schema. write, export, and browser-task tools are unavailable through this action, and discover current sellerspace fields for advanced selection, filtering, sorting, or output interpretation in a supported data domain. 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 SellerSpace account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SellerSpace capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_ad_metric_historyREADGet time-series or placement-level metrics for one SellerSpace advertising campaign, ad group, promoted product, keyword, target, or search term.
INPUTS: sellerId / marketplace / adDataType / id / fromDateStr
call_toolREVIEWCall an explicitly approved SellerSpace MCP read tool with JSON arguments after discovering its live schema. Write, export, and browser-task tools are unavailable through this action.
INPUTS: toolName / arguments
discover_fieldsREVIEWDiscover current SellerSpace fields for advanced selection, filtering, sorting, or output interpretation in a supported data domain.
INPUTS: domain / entity / query / usage
list_fba_shipmentsREADList SellerSpace FBA inbound shipments with status, warehouse, quantities, and SKU-level receiving differences for one Amazon store and marketplace.
INPUTS: sellerId / marketplace / merchantId / shipmentId / shipmentStatus
list_storesREADList Amazon stores and marketplaces authorized in SellerSpace so their seller IDs and marketplace codes can be used in subsequent queries.
INPUTS: refresh / keywords / sellingRegion / authAvailable / mwsAvailable
list_toolsREADDiscover SellerSpace tools approved by Connector for read-only dynamic calls, including their live input schemas and behavior annotations.
query_adsREADQuery SellerSpace Amazon advertising campaigns, ad groups, promoted products, keywords, targets, search terms, or negative targeting with filters and pagination.
INPUTS: entity / scope / period / name / status
query_productsREADQuery SellerSpace product performance or long-term storage fee data across one or more Amazon store-marketplace stations.
INPUTS: scope / period / criteria / view / fields
query_store_performanceREADQuery SellerSpace store or marketplace performance, including orders, revenue, profit, refunds, advertising spend, FBA fees, ROI, and ACoS.
INPUTS: scope / period / criteria / view / fields
INPUT CONTRACTS
Know what the action needs before it runs.
get_ad_metric_history
sellerIdREQUIRED- The SellerSpace seller ID returned by list_stores.
marketplaceREQUIRED- The marketplace code returned by list_stores.
adDataTypeREQUIRED- The advertising entity type.
idREQUIRED- The entity ID returned by query_ads; use a string for large IDs.
fromDateStrREQUIRED- The query start date.
call_tool
toolNameREQUIRED- The exact tool name returned by list_tools.
argumentsOPTIONAL- JSON arguments matching the inputSchema returned for the selected tool.
discover_fields
domainOPTIONAL- The SellerSpace field domain.
entityOPTIONAL- An optional entity context such as campaign, product, market, or store.
queryOPTIONAL- A field name, keyword, or business meaning to search for.
usageOPTIONAL- The intended field usage.
list_fba_shipments
sellerIdREQUIRED- The SellerSpace seller ID returned by list_stores.
marketplaceREQUIRED- The marketplace code returned by list_stores.
merchantIdOPTIONAL- The optional Amazon merchant ID.
shipmentIdOPTIONAL- An exact FBA shipment ID.
shipmentStatusOPTIONAL- The FBA shipment status.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Ad Metric History
Get time-series or placement-level metrics for one SellerSpace advertising campaign, ad group, promoted product, keyword, target, or search term. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_ad_metric_historyVerify with List Fba Shipments
List SellerSpace FBA inbound shipments with status, warehouse, quantities, and SKU-level receiving differences for one Amazon store and marketplace. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_fba_shipmentsSAFETY BOUNDARY
Operate SellerSpace with explicit limits
- Authorize SellerSpace with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned SellerSpace 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 SellerSpace rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SellerSpace task completed successfully.
CONNECTION MODEL
API key
SellerSpace MCP key sent in the x-api-key header. Create it by following https://www.sellerspace.com/help/doc/how-to-get-your-sellerspace-mcp-key .
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
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
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 SellerSpace.