Skip to content
Get MCP AdsGet MCP Ads, home
Start free
skills/google-shopping-dashboard.md

RecipeGoogle Ads

Build a Google Shopping dashboard in Claude

Builds the Get MCP Ads Google Shopping template as a Claude dashboard: Shopping KPIs against an equivalent comparison period, a brand map, top and rising brands, products spending without selling, movers and the full product table.

IntentA live Shopping report by brand, product and product type that shows where the feed earns and where it burns.

3
Steps
1
Tools
3
Rules
1
Failure modes

When to use it

Use it when

  • Someone asks for a Shopping dashboard, a product or brand performance report, or a feed review they can keep in Claude.

Do not use it when

  • One product's figures: answer in the conversation.
  • Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.

What it needs first

Required

Preconditions

  • The organisation is on Team or Enterprise: ready-made dashboards are not offered on Free or Pro.
  • The account is ticked in the dashboard, confirmed via list_accounts.

Inputs

window
Analysis window.Default: last 30 days.

Procedure

In order. Every tool named is one the gateway ships, and links to its reference.

  1. Resolve the client's Google Ads account with Shopping campaigns with list_accounts.

  2. Fetch the google-shopping template for that account.

  3. Create a Dashboard artifact, write every document exactly as given in one batch, read its check, hand over with the lines given.

Decision rules

The observable condition, what it lets you conclude, and what takes the conclusion back.

  • When

    The template is refused with PLAN_REQUIRED

    Conclude

    Say the dashboards come with Team and Enterprise and that only the account owner changes the plan; answer the question in the conversation meanwhile.

  • When

    The account runs no Shopping or Performance Max with a feed

    Conclude

    Say the template needs Shopping product data and offer the Performance Max or scorecard dashboard instead.

  • When

    A reader sees a source fail to load

    Conclude

    Their own Get MCP Ads access decides: check that their connection covers this client's workspace and that their plan includes dashboards before changing the dashboard.

Evidence every conclusion must carry

  • Every figure carries its account, metric and window.
  • Anything below a readable sample size is reported as unjudged, not as zero.

Where the agent stops

  • The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

How it goes wrong quietly

The cases where the analysis is wrong and still looks right. Read them before trusting a number.

  • Editing the template's page or queries by hand loses the provenance of each figure: ask for changes by name instead.

What the answer contains

01Readout
The figures, with windows and accounts named.
02Flags
What deserves a deeper skill or a human decision.