1stPage

Amazon Brand Analytics — Search Query Performance (SQP) and the ICAP funnel. Use for search-share, keyword-ranking, and search-funnel questions: "which keywords drive my ASIN", "how do I rank for a term", "am I gaining or losing search share", "which keywords should I advertise". Works for seller accounts and for vendor accounts with SQP reports enabled. Select a report via `dataset`. Weekly data; list datasets paginate via limit/offset or cursor.

Create a recurring 1stPage report: 1stPage runs the saved prompt on schedule and delivers the answer by email and/or Slack to the emails and/or slack_channel_ids you pass. Use for "send/email me this report every day at 8am", "weekly digest to Slack". Times are LOCAL to the given IANA timezone (DST-safe). If the user gives no timezone and none is on their profile, ask for it. If the user has not stated WHERE to deliver (a concrete email address and/or Slack channel), ask — never invent or reuse an address they did not give. When writing the saved prompt, prefer "the most recent complete day" over a literal "yesterday" — settled Amazon reports lag 2-3 days and phrasing it this way keeps every occurrence useful. Always confirm the resolved schedule (time + timezone + next run) back to the user. Scheduled runs can only READ data — the saved prompt cannot change settings or create further schedules.

Permanently delete a recurring 1stPage report. This cannot be undone; pause_schedule stops a report and keeps it. Use for "delete my weekly digest". Call list_schedules first to get the schedule_id, and confirm with the user before deleting.

Customer Amazon Inventory data for seller and vendor accounts. Select health, restock, merchant_items, sales_summary, open_shipments, awd_shipments, category_forecasts, or storage_fees.

List all Amazon seller accounts the user has access to, along with their marketplaces. Use this first to discover available account_id and market_place_id values before calling other tools. Accounts may carry a user-assigned nickname — when the user refers to an account by a familiar name, match it against both nickname and name.

List the notification/alert settings for an account — every available notification type with whether it is configured, enabled or muted, and where it is delivered (email addresses and Slack channel IDs). Use this for "what alerts do I have set up", "is the out-of-stock alert on", or before changing anything with set_notification. IMPORTANT: report counts and which alerts are on/off from the `summary` object (total, enabled, disabled, enabled_names, disabled_names) — do not tally `data` yourself.

List the user's scheduled tasks (recurring AI reports delivered by email/Slack) with their schedule, delivery targets, status, and last run outcome. Use this for "what schedules do I have", "did my digest run", "why didn't I get my report", and always before updating, pausing, resuming or deleting a schedule to get its schedule_id.

Read the deterministic Listing Quality scorecard, ASIN findings, scan freshness, and human-approved Amazon update queue. Scores are point-in-time structural checks, not AI judgments. The summary labels the strict complete-data score and coverage, a broader provisional score when partial-source listings are available, and current processing/backoff state. Use view=summary for the account score, items for ranked ASINs, item for one ASIN, updates for the write queue, or update for one queued change.

Pause a recurring 1stPage report: it stops running and delivering until resume_schedule turns it back on. Use for "pause my daily digest", "stop the weekly report for now". Call list_schedules first to get the schedule_id, and confirm the new status back to the user.

Add keywords for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: keyword_tracking:write.

Brands for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: read.

History for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: read.

Keywords for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: read.

Products for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: read.

Results for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: read.

Update keywords for Amazon organic keyword tracking. Use brand discovery for IDs and supported profile. Reads return stored observations and never trigger paid searches. Adding active keywords schedules future daily checks against selected owned ASINs and consumes tracking allowance. Mutations require company admin and keyword_tracking:write; use dry_run to preview. Required scope: keyword_tracking:write.

Resume a paused recurring 1stPage report: it runs again from its next scheduled time and delivers to its email/Slack recipients. Use for "turn my weekly report back on". Call list_schedules first to get the schedule_id, and confirm the next run back to the user.

Amazon Seller (3P) analytics — sales, traffic, orders, and inventory. START HERE for most seller questions. Select a report via `dataset` (see its enum for the intent→dataset guide). Quick routing: sales/revenue/units/product rankings/comparisons → real_time_sales; broad business overview that explicitly includes traffic or advertising → portfolio_summary; sessions/conversion/refunds or settled report history → daily_trend/settled_daily_sales/asin_sales_ranking; stock risk → inventory_health; category rollups/share-of-category → category_performance. For listing score/findings/update queue use the top-level listing_quality tool. For keyword/search-share questions use the brand_analytics tool. Defaults: date_range=last_30_days, limit=20. List datasets paginate via limit/offset or cursor.

Create or update a notification/alert for an account — turn it on or off and set where it is delivered (email addresses and/or Slack channel IDs). Only the fields you pass are changed. Use this for "alert me when X happens", "turn on the out-of-stock alert", "send account health alerts to this channel", or "mute this alert". Call list_notifications first to see valid notification_type values and the current state.

Change a recurring 1stPage report. Only the fields you pass change; emails, slack_channel_ids and days_of_week replace the existing lists. The time stays local to the schedule's timezone unless you pass timezone. Use for "change it to 7am", "send it to our Slack channel instead". Call list_schedules first to get the schedule_id. Pass only email addresses and Slack channels the user stated; never invent or reuse one. Always confirm the resolved schedule (time + timezone + next run) back to the user. Scheduled runs can only READ data — the saved prompt cannot change settings or create further schedules.

Amazon Vendor (1P) analytics — ordered/shipped/product revenue, sourcing share, and inventory. Select a report via `dataset`. List datasets (…_by_asin, product_revenue, revenue_by_period, inventory_by_asin) support pagination via limit/offset or cursor and return a pagination block. For Search Query Performance / search-share questions on this vendor account, use the brand_analytics tool (available when SQP reports are enabled).