Get the optimization playbook
get_optimization_guideThe app's feed optimization playbook. Without section, lists every section with its summary and current affected count so you can pick where to start. With a section id (issues, titles, descriptions, images, identifiers, categories, price-availability, details, bundles, shipping, campaigns), the full guide: rules, checklist, examples, and which attributes to change. Read the relevant guide BEFORE proposing changes to any feed attribute it covers.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_optimization_guide"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| section | No | Omit for the section overview, or pass one section id for its full playbook |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Plain-language result or next step, safe to read out to the merchant. | |
| guide | No | The full playbook for the requested section | |
| sections | No | Every section with its summary and affected count | |
| issueGroups | No | Item-level issue codes, on the issues section | |
| fieldWideFix | No | When to prefer one mapping over per-product overrides | |
| accountIssues | No | Account-level issues, on the issues section | |
| affectedCount | No | Products the requested section currently flags | |
| totalProducts | No | Products in the feed the counts were taken against | |
| countsIssueRows | No | Only on the issues section: affectedCount counts issue rows, not products. list_section_products and optimize_next count sample products | |
| mappableAttributes | No | Attributes in this section that a mapping rule can fix catalog-wide | |
| searchDataAvailable | No | False when Search Console data has not been synced, so title advice is generic |