# aplusContent_list_documents_detailed (https://sellersheetai.com/docs/mcp-api/tools/aplusContent_list_documents_detailed)

> Up to 50 A+ Content documents per call (5 pages × 10 records), each enriched with its full contentDocument JSON and linked ASINs — sheet-ready rows for the "List A+" tab.

Access: **READ** · toolset amazon_sp · family sp.aplusContent_2020-11-01

Each record costs two enrichment calls (aplusContent_getContentDocument and the ASIN relations), ~100 per batch, on purpose. aplusContent_searchContentDocuments first says how many documents exist; then call without pageToken, write data.rows, and repeat with data.nextPageToken until it is absent. Amazon SP-API · searchContentDocuments · GET /aplus/2020-11-01/contentDocuments Amazon SP-API · getContentDocument · GET /aplus/2020-11-01/contentDocuments/{contentReferenceKey} Amazon SP-API · listContentDocumentAsinRelations · GET /aplus/2020-11-01/contentDocuments/{contentReferenceKey}/asins

## Call it

MCP tool call:

```json
{
  "name": "aplusContent_list_documents_detailed",
  "arguments": {
    "store": "myStore-US"
  }
}
```

Tool API (early access — contact us):

```bash
curl -X POST https://api.sellersheetai.com/api/v1/tools/aplusContent_list_documents_detailed \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"store":"myStore-US"}'
```

## Arguments

| Name | Type | Required | Description |
|---|---|---|---|
| `store` | string | yes | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
| `pageToken` | string |  | the previous call's data.nextPageToken; omit for the first page. |
| `maxPages` | integer |  | the batch size in tens, 1–10 (default 5 → at most 50 records enriched); Amazon decides a page's size, so the records beyond maxPages×10 come back as data.unenriched_keys. Lower it for a smaller batch. |

## Result

- `data.count` — rows in this batch.
- `data.unenriched_keys` — the page's remaining contentReferenceKeys when Amazon's page was larger than the batch — fetch each with aplusContent_getContentDocument.
- `data.rows` — one per document — {name, status DRAFT | SUBMITTED | APPROVED | REJECTED (suspended content reverts to DRAFT), updateTime ('YYYY-MM-DD HH:MM:SS'), badgeSet (comma-separated: BULK, GENERATED, LAUNCHPAD, PREMIUM, STANDARD), marketplaceId, contentReferenceKey, contentDocument (JSON string of the document itself — parse it and pass it to aplusContent_updateContentDocument; "error: <reason>" when that fetch failed), contentDocumentAsinRelations (every linked ASIN, newline-separated; "error: <reason>" when the enrichment failed)}.
- `data.nextPageToken` — only when more batches exist.

## Params (Amazon schema; searchContentDocuments)

- marketplaceId*: string pageToken: string

## Params (Amazon schema; getContentDocument)

- contentReferenceKey*: string marketplaceId*: string includedDataSet*: CONTENTS | METADATA (list)

## Params (Amazon schema; listContentDocumentAsinRelations)

- contentReferenceKey*: string marketplaceId*: string includedDataSet: METADATA (list) asinSet: [string] pageToken: string

## Workflow

- 1. Write data.rows from row 5 of the "List A+" tab: row 1 = the key headers (name | status | updateTime | badgeSet | marketplaceId | contentReferenceKey | contentDocument | contentDocumentAsinRelations), row 2 = the "Store" label (do not overwrite), row 3 = the store value, row 4 = the display headers (A+ Name | Status | Update Time | Badge Set | Marketplace ID | Content Reference Key | Content Document | ASINs).