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

Recipe

Build a cross-platform scorecard dashboard in Claude

Builds the Get MCP Ads Cross-platform scorecard as a Claude dashboard: spend, conversions, ROAS, CPA, CTR and CPC per platform against an equivalent comparison period, spend blended per currency, each platform's own conversions named and never added up, and GA4 site revenue, purchases, MER and channel mix when connected.

IntentOne live page that puts every ad platform of a client side by side, with the site's own truth from GA4.

3
Steps
1
Tools
3
Rules
2
Failure modes

When to use it

Use it when

  • Someone asks for a cross-platform dashboard, a scorecard of all their ad platforms, or a Looker Studio style overview they can keep in Claude.
  • A weekly or monthly all-platform review the team opens without asking again.

Do not use it when

  • A single number across platforms right now: answer in the conversation.
  • Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.

What it needs first

Optional

No single source is required: this one reads across whatever you have connected.

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 workspace and its ad accounts, one per platform, plus its GA4 property when connected, with list_accounts.

  2. Fetch the scorecard template with every account (accounts, one per platform, GA4 included).

  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 client has no GA4 property connected

    Conclude

    Build the scorecard on the ad platforms alone and say the site revenue, MER and channel views appear once GA4 is connected.

  • 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.
  • Summing the platforms' conversions or revenue double counts the orders they all claim: the scorecard shows them side by side on purpose.

What the answer contains

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