fbaInbound_get_plan_status
List every placement option of an inbound plan (all pages) — a quick existence and stage probe before a phase.
readAmazon Seller (SP-API)sp.fulfillmentInbound_2024-03-20
For the plan's own status and shipments use fbaInbound_getInboundPlan. Amazon SP-API · listPlacementOptions · GET /inbound/fba/2024-03-20/inboundPlans/{inboundPlanId}/placementOptions Use this at the start of each phase to validate _state before taking irreversible actions.
Call it
In an AI client (MCP)
{
"name": "fbaInbound_get_plan_status",
"arguments": {
"store": "myStore-US",
"plan_id": "<plan_id>"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/fbaInbound_get_plan_status \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","plan_id":"<plan_id>"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
plan_idrequired | string | the inboundPlanId (from fbaInbound_createInboundPlan or fbaInbound_listInboundPlans). |
Result
Every tool answers {notification, data, human_action}; data carries:
data.planId— the plan ID.data.placementOptions— ALL placement options — this compound scans every page deliberately (it is an existence/state probe). For a paged read use fbaInbound_listPlacementOptions.
Workflow
- 1. Read _state tab: stage and planId 2. Call this tool with the stored planId 3. If placement options empty → plan may not exist or stage < PACKING_GENERATED 4. If API error → reconcile with human before proceeding
Params (Amazon schema)
inboundPlanId*: string (max 38 chars)
pageSize: integer (1–20)
paginationToken: string (max 1024 chars)