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

> Run a saved AMC workflow on a schedule — Daily or Weekly — on the store's instance.

Access: **WRITE** · toolset amazon_ads · family ads.amc-reporting

Each run appears in ads_list_workflow_executions (filter by its workflow_id). Ask the seller first. Amazon Ads API · createSchedule · POST /amc/reporting/{instanceId}/schedules Docs: https://advertising.amazon.com/API/docs/en-us/amc-reporting#tag/Schedules/operation/createSchedule Gate: approve — interactive: show the change (Amazon's preview first where one exists), wait for an explicit approve; autopilot: only when the seller's own words asked for this change; otherwise ask.

## Call it

MCP tool call:

```json
{
  "name": "ads_create_schedule",
  "arguments": {
    "store": "myStore-US",
    "country_code": "<country_code>",
    "body": {}
  }
}
```

Tool API (early access — contact us):

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

## 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. |
| `country_code` | string | yes | the Ads profile's 2-letter country code (e.g. 'US'). |
| `body` | object | yes | the request body — its fields, enums and required marks are in this parameter's schema. scheduleId, workflowId (a saved workflow) and aggregationPeriod are needed; scheduleEnabled false saves it paused. The marketplace is the store's. |

## Result

- `data.schedule_id` — the schedule's id.
- `data.workflow_id` — the workflow it runs.

## Gotchas

- A run's result can be downloaded for about a day; read each run in time.
- A synced report's schedule or workflow (data.synced_ids of the two list tools) is refused.