Skip to main content
Glama

Visibility Genies

Read Google Ads landing pages

get_google_ads_landing_pages
Read-only

The landing pages of the connected Google Ads account's ads that brought paid conversions in a period, from what the daily pull stored: clicks, cost, conversions and cost per conversion, most conversions first, with the page's organic clicks, impressions and average position from Search Console over the same days (null where Search Console has none for the page; organicState says whether it was read). Landing page numbers reach back about 90 days (numbersStartOn says from when). Money is in the account's currency (currencyCode). Read-only; uses no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_google_ads_landing_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 100, max 500).
rangeNoA named period ending on the last stored day (default last_3_months). Ignored when startDate and endDate are given.
endDateNoLast day (YYYY-MM-DD). Use with startDate; at most 730 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the Ads account's time zone).

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
rowsNo
reasonNo
endDateNo
hasMoreNo
messageNo
failedAtNo
rowCountNo
startDateNo
connectUrlNo
storedFromNo
accountNameNo
currencyCodeNo
organicStateNo
storedThroughNo
numbersStartOnNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds substantive behavior beyond them: a ~90-day data horizon with numbersStartOn, default sort by most conversions first, null handling for missing Search Console rows with an organicState flag, currency coding, and the explicit 'uses no credits' billing note.

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?

Front-loaded with the resource and the metric list, then the Search Console caveats and limits, then the read-only/credits note. Nearly every clause carries new information, though the main sentence is heavily stacked and could be split for readability.

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

Completeness5/5

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

With an output schema present, the description needn't enumerate return fields, and it still covers the essentials an agent needs: data source and freshness limits, sort order, currency, null semantics, and cost model. Nothing material is missing for correct invocation.

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 baseline is 3, but the description adds real meaning the schema lacks — that the stored history only reaches back about 90 days (so wide range values like last_12_months exceed available data) and that money is in the account's currency. It does not explain the startDate/endDate vs range precedence, which the schema does handle.

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?

States a precise verb+resource ('landing pages of the connected Google Ads account's ads') and immediately scopes it to ads that 'brought paid conversions in a period,' which cleanly separates it from organic landing-page siblings. The listed metrics (clicks, cost, conversions, cost per conversion plus Search Console organic data) make the payload unambiguous without opening the output schema.

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

Usage Guidelines3/5

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

Usage is implied: call this to get paid landing-page performance with organic context. It never names a boundary or alternative (e.g. get_google_analytics_organic_landing_pages, get_landing_page_insights) nor states when-not to use it, leaving routing to inference.

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.

Resources