First Meta review

This is the canonical first workflow after setup.

It is intentionally narrow: one read-only review, one account, one clear output shape.

Local adcom path

Use this when your agent is connected through the local adcom bridge.

adcom login
adcom mcp serve

Then ask the agent to:

1. Call meta_get_ad_accounts
2. Pick an accessible account_id
3. Call meta_review_account_performance with that explicit account_id

The local bridge proxies the hosted tool surface unchanged. There is no local review wrapper.

Hosted MCP path

Use this when you are connecting to the hosted MCP surface directly instead of going through adcom.

The hosted path uses the same tools:

meta_get_ad_accounts
meta_review_account_performance

with:

{
  "account_id": "act_123"
}

Optional inputs:

• lookback_days
• top_campaign_limit
• top_ad_set_limit

Output shape

The review returns:

• review_window
• account_summary
• top_campaigns
• top_ad_sets
• flagged_campaigns
• flagged_ad_sets

What the workflow flags

The current review uses deterministic finding codes:

• spent_without_clicks
• low_ctr_vs_account_average
• high_cpc_vs_account_average

This workflow does not make writes. It is the proving ground for the first operational read, not an automation runner.