Client: where ads should send people, from 90 days of every source
landing_evidenceBefore deciding where ads send people (a new campaign, ad, sitelink or landing page, or a page edit made for ads), pull everything in one call: 90 days of Google Ads clicks and conversions by landing page (sitelinks included), ad groups and top search terms; Analytics sessions, engagement and leads by landing page and channel on every property the client has; Search Console clicks per page; and hosted-form leads by page and source. Gives the best converting paid page. With url: also reads that live page (form, phone, towns it names) and says whether it has paid conversion history and whether it is a dedicated landing page; with ad_texts, whether the page backs what the ad says. Cite these numbers in any build plan.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"client": "<client>"
},
"name": "landing_evidence"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | A landing page you are considering | |
| fresh | No | Re-read now instead of using the copy from the last 6 hours | |
| client | Yes | Client name from list_clients | |
| ad_texts | No | Headlines and descriptions you plan to use, to check against the page | |
| campaign_theme | No | What the campaign sells, e.g. 'custom sheds Snohomish County' |