Update to Adzviser Amazon Ads

{
  "description": "Open an interactive Amazon Ads report so the user can inspect, edit and run the reporting request. Use only for an explicit Preview UI, UI Mode, embedded or interactive report request. Use Data Mode for ordinary numeric questions, calculations and comparisons.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 248
    }
  ],
  "name": "adzviser-preview-ui-mode",
  "skill_md_contents": "---\nname: adzviser-preview-ui-mode\ndescription: Open an interactive Amazon Ads report so the user can inspect, edit and run the reporting request. Use only for an explicit Preview UI, UI Mode, embedded or interactive report request. Use Data Mode for ordinary numeric questions, calculations and comparisons.\n---\n\n# Amazon Ads Preview UI\n\nUse `preview_and_retrieve_reporting_data` only for an explicitly requested\ninteractive report. Ordinary spend, clicks, campaign and trend questions use\n`retrieve_reporting_data` through the Data Mode skill.\n\nCall `list_workspace` and select the named Amazon Ads workspace. Ask when no\nworkspace is named and multiple suitable choices remain. Call\n`list_metrics_and_breakdowns_amazon_ads` for exact fields and request only what\nis necessary. Resolve relative dates from the current date: last week is the\nprevious complete Monday-Sunday week unless otherwise specified. Respect the\nsource reporting timezone and the current 60-day start-date lookback limit.\nExplain unsupported dates instead of silently changing the requested period.\n\nWhen the user asks for an N-day period ending two days ago, let D be the current\ndate in the user's timezone and use [D-(N+1), D-2], inclusive. For seven days use\n[D-8, D-2]; its preceding comparison period is [D-15, D-9]. Exclude yesterday\nand today, state the actual dates, and do not substitute a calendar week.\n\nSend one `adzviser_request` with `workspace_name`, inclusive `date_ranges`,\noptional `time_granularity`, and `assorted_requests.amazon_ads_request` containing\n`metrics` and optional `breakdowns`. No other data-source keys are supported.\nDo not include conversation history, the raw prompt, unrelated context,\ncredentials, personal identifiers or caller-selected destinations. Do not send\n`client_id`, `reporting_mode` or `_widget_action`; mode controls are app-only.\nDo not invent filter, sorting, limit or other undeclared arguments.\n\nKeep monetary values in their reported currencies, distinguish campaigns with\nIDs when names repeat, and retain attribution windows for purchases, sales,\nACOS and ROAS. Use `time_granularity` for a time series. Preserve missing data\nand assumptions rather than inventing zeros or complete coverage.\n\nOpen the preview once and let the component handle editing, Run and mode controls.\nThe initial preview is not a completed report. Do not immediately follow it with\ndirect retrieval or claim to analyze hidden component state. Analyze only rows\nmade visible to the model and use Data Mode when the user asks for raw data.\nIf reporting is still being prepared, surface that state honestly; opening the\npreview does not bypass backend data availability.\n\nThe plugin does not edit campaigns, bids or budgets, purchase ads or products,\nchange store listings, or reveal individual shoppers' names or contact details.\nA reporting preview must not be presented as completing any such action.\n"
}