Adzviser Google Ads

View saved version →

---
name: adzviser-data-mode
description: Retrieve and analyze reporting from the user's connected Google Ads accounts with Adzviser. Use for spend, clicks, conversions, campaign comparisons, trends, raw rows and Data Mode. Public competitor ad-library searches and ad-account changes are not supported.
---

# Google Ads Data Mode

Call `retrieve_reporting_data` for questions about numbers. Use the preview
skill only for an explicitly requested interactive report; do not open a widget
after a successful direct retrieval merely to display the same request.

## Minimal report request

1. Call `list_workspace` without arguments. Use the user's named workspace. If
   it is unavailable, explain the access problem rather than substituting one.
   When multiple suitable workspaces exist and none was named, ask which to use.
2. Call `list_metrics_and_breakdowns_google_ads` without arguments and use the
   exact returned field labels. Request only metrics and dimensions needed for
   the user's question; do not select an entire catalog or default to all data.
3. Resolve inclusive YYYY-MM-DD date pairs using the current date. Last month is
   the previous complete calendar month; last week is the previous complete
   Monday-Sunday week unless the user specifies otherwise. Report dates follow
   the source account's reporting timezone, not an invented UTC conversion.
4. Send `adzviser_request` with `workspace_name`, `date_ranges`, optional
   `time_granularity`, and `assorted_requests.google_ads_request` containing
   `metrics` and optional `breakdowns`. Include both periods in one comparison
   request. No other source keys are supported by this plugin.
5. Inspect each header and row under
   `structuredContent.reportingData.GoogleAds.data`. Results are grouped into
   tables such as Account or Campaign; `data` is not itself a single flat table.
   Surface relevant `note_of_assumption` text.

Never send the full conversation, chat history, raw user prompt, unrelated
context, credentials, email addresses or session tokens as report inputs. Select
field names and dates from the question instead. `reporting_mode=data` is routing
intent, not a tool argument. Do not send `client_id`, `reporting_mode` or
`_widget_action`; `set_reporting_mode` is an app-only preference control.

## Google Ads interpretation

- Cost, Clicks, Impressions and Conversions are valid examples; confirm current
  labels through discovery. Do not guess similar labels or invent filters,
  query text, sorting, limits, arbitrary URLs or a natural-language input field.
- Include Account Currency Code when reporting monetary amounts. Keep currencies
  separate. Cost can be returned as `$ Cost`; use the actual column header and
  currency, and do not divide an already formatted amount by a million again.
- Use Campaign ID with Campaign Name to distinguish campaigns. Additional source
  context columns may be returned; summarize only what answers the question.
- Conversions can be fractional due to attribution. Do not round them to whole
  people, substitute All Conversions, or call conversion value collected revenue.
- For CTR, request Clicks and Impressions and calculate clicks / impressions × 100.
  Use N/A for a zero denominator; aggregate from totals rather than averaging
  percentages. Use the returned units for other rates and ROAS.
- Use `time_granularity` for Date, Week, Month or Quarter rather than adding those
  labels to breakdowns. Daily dates may be returned in a Date Range column.
- Empty/header-only tables mean no matching returned rows. Do not invent zero
  rows for missing dates or groups. A zero comparison baseline has no finite
  percentage change. Distinguish a partial period from a complete one.
- Never use `google_ads_transparency_request` here. The plugin supports connected
  account performance, not competitor or public-ad searches. It cannot edit
  campaigns, change bids/budgets, publish ads, make purchases or delete records.

For an unsupported field, refresh discovery and correct the request once. For
an authentication or access error, explain the returned issue without claiming
the report succeeded. Reuse successful rows instead of repeating the request.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: adzviser-preview-ui-mode
description: Open an interactive report for the user's connected Google Ads account so they can inspect, edit and run it. Use only for an explicit Preview UI, UI Mode, embedded or interactive report request. Use Data Mode for ordinary numeric questions and calculations.
---

# Google Ads Preview UI

Use `preview_and_retrieve_reporting_data` only when the user explicitly wants
an interactive report. Ordinary spend, performance, audit and comparison
questions use `retrieve_reporting_data` through the Data Mode skill.

Call `list_workspace` and `list_metrics_and_breakdowns_google_ads` without
arguments. Select the named workspace and exact requested metric/breakdown
labels. If access is unavailable, explain the problem without substituting a
different workspace. Resolve dates from the current date: last month is the
previous complete calendar month; last week is the previous complete
Monday-Sunday week unless otherwise requested.

Send one `adzviser_request` with `workspace_name`, inclusive `date_ranges`,
optional `time_granularity`, and `assorted_requests.google_ads_request` containing
`metrics` and optional `breakdowns`. Include only fields and dates needed for
the report. Never include the full conversation, raw prompt, chat history,
unrelated context, credentials or caller-selected destinations. Do not send
`client_id`, `reporting_mode` or `_widget_action`; the mode tool is app-only.

Use Account Currency Code for money and keep currencies separate. Cost can be
returned as `$ Cost` and is already formatted; do not convert it from micros
again. Conversions may be fractional. Include Campaign ID when distinguishing
campaigns. Use `time_granularity` for daily/weekly/monthly/quarterly reports,
not an invented time breakdown. Do not invent arbitrary filters or source keys.

Open the preview once and let the component handle editing, Run and mode
controls. The initial preview is not a completed report. Do not immediately
follow it with a direct retrieval or claim to have analyzed hidden component
state. Analyze only rows actually published to the model; if the user asks for
raw data, use Data Mode. Preserve returned assumptions and no-data results.

This plugin does not change campaigns, budgets or bids, publish ads, delete
records or search the public Google Ads Transparency Center. Explain those
limits without treating a report as a substitute for an unsupported action.

Referenced files: 1 — file references are metadata, not package contents.