Skip to main content
Glama

Client: where ads should send people, from 90 days of every source

landing_evidence
Read-onlyIdempotent

Before 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

NameRequiredDescriptionDefault
urlNoA landing page you are considering
freshNoRe-read now instead of using the copy from the last 6 hours
clientYesClient name from list_clients
ad_textsNoHeadlines and descriptions you plan to use, to check against the page
campaign_themeNoWhat the campaign sells, e.g. 'custom sheds Snohomish County'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: exactly which data sources are aggregated, that it returns the best converting paid page, and that with url it reads the live page to check form/phone/towns and paid conversion history. It does not mention the 6-hour cache behavior (left to the schema's fresh parameter), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary usage condition and data sources, and every sentence is informative rather than repetitive. It is slightly dense with semicolons and long clauses, but the density is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the multi-source aggregation, rich schema coverage, and absent output schema, the description is complete enough for correct invocation. It explains what is pulled and what optional checks do, though it does not describe the response shape in detail. An agent can still call it correctly and interpret the high-level result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning for url ('also reads that live page... says whether it has paid conversion history and whether it is a dedicated landing page') and ad_texts ('whether the page backs what the ad says'), which goes beyond the schema's terse field descriptions. campaign_theme and fresh are not mentioned, but their schema descriptions are sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('pull everything') and resource ('90 days of Google Ads clicks and conversions by landing page... Analytics sessions... Search Console clicks... hosted-form leads'), making it clear this is a cross-source evidence-gathering tool. It is easy to distinguish from siblings like ads_report, ga4_report, or site_check because it explicitly aggregates all of those sources in one call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear when-to-use condition: 'Before 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.' It also specifies downstream usage ('Cite these numbers in any build plan'). It does not explicitly name alternatives or when not to use it, so a 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.