# A+ Content (https://sellersheetai.com/docs/mcp-api/workflows/aplus)

> Check, create, iterate and publish A+ content — and manage which ASINs it is live on — without opening Seller Central.



<Callout title="In short">
  Your agent checks whether an ASIN already has A+, builds and submits a whole module set in one call, edits drafts, relinks variation families and takes content down without deleting it.
</Callout>

## In your daily workflow [#in-your-daily-workflow]

<Steps>
  <Step>
    ### Before writing anything [#before-writing-anything]

    "Does this ASIN already have A+?" `aplusContent_searchContentPublishRecords` answers per ASIN, so you never draft content that would fight a live document.
  </Step>

  <Step>
    ### Launch day [#launch-day]

    `aplusContent_create_and_publish` is the one-call pipeline: it uploads your images, creates the document, links the ASINs and submits it for Amazon's review.
  </Step>

  <Step>
    ### Iterate on a draft [#iterate-on-a-draft]

    `aplusContent_updateContentDocument` edits copy and modules while the document is still a draft; `aplusContent_postContentDocumentApprovalSubmission` sends it for review when you are happy.
  </Step>

  <Step>
    ### Manage a variation family [#manage-a-variation-family]

    New variation added? `aplusContent_validateContentDocumentAsinRelations` checks the ASINs first, then `aplusContent_postContentDocumentAsinRelations` replaces the linked set.
  </Step>

  <Step>
    ### Review the portfolio, take content down [#review-the-portfolio-take-content-down]

    `aplusContent_list_documents_detailed` pulls your documents with full detail, so your agent can lay out coverage brand-wide in a sheet. `aplusContent_postContentDocumentSuspendSubmission` unpublishes a document and keeps it for later.
  </Step>
</Steps>

## Try asking [#try-asking]

> "Check if B0EXAMPLE1 already has live A+ content, then create and publish A+ for it using the images in my Images Generation sheet."

> "Create the A+ page from the content in my sheet and submit it."

## Step 1, both ways [#step-1-both-ways]

The same tool and the same arguments — through your AI client, or from your own code.

**MCP** — you ask: "Does B0EXAMPLE1 have A+ yet?" Your agent calls `aplusContent_searchContentPublishRecords` and tells you what is live.

<ToolCall tool="aplusContent_searchContentPublishRecords" args="{ asin: &#x22;B0EXAMPLE1&#x22; }" />

<Callout type="warn" title="Write access required">
  Creating, editing, submitting, linking and suspending change your seller account, so the store needs write access (see [Stay in control](/docs/mcp-api/control)). Searching and reading documents works with read access.
</Callout>

## Tools on this page [#tools-on-this-page]

Pulled from the catalog at build time, each with its own access label.

<ToolList domains="[&#x22;aplusContent&#x22;]" />

## FAQ [#faq]

### Where do the A+ images come from? [#where-do-the-a-images-come-from]

From your own files, or from images your agent generates — see [AI images](/docs/mcp-api/workflows/images). Generated images are paid from Credits.

### What should the copy say? [#what-should-the-copy-say]

Ask your agent to start from what buyers say — see [Review insights](/docs/mcp-api/workflows/reviews).