Skip to main content
Glama

Visibility Genies

Read organic landing pages

get_google_analytics_organic_landing_pages
Read-only

Organic Search landing pages from Google Analytics with sessions, engagement, key events and ecommerce outcomes: use it for what organic visitors did on the site. get_landing_page_insights puts each page beside its Search Console clicks, and get_search_opportunities picks the pages closest to winning more clicks. Read only and free. Defaults to the last 28 complete property days.

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_analytics_organic_landing_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
deviceNoOnly this device: desktop, mobile or tablet.
mediumNoOnly sessions whose medium contains this text, in any case.
offsetNo
sourceNoOnly sessions whose source contains this text, in any case.
countryNoOnly this country, as its two-letter ISO code, for example DE.
endDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
campaignNoOnly sessions whose campaign contains this text, in any case.
keyEventNoCount only this key event (for example purchase) in the key event columns, instead of all key events. Not for the key events report, which lists them by name.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
channelGroupNoOnly this Google default channel group by its exact name, for example Paid Search, Organic Social or AI Assistant. Pass channel=all where the tool has it, or Organic Search is all that is read.
pageContainsNoOnly pages whose address contains this text, in any case. Not for site search or ecommerce by item.

Output Schema

NameRequiredDescriptionDefault
rowsNo
errorNo
quotaNo
sourceNo
statusYes
requestNo
pageInfoNo
rowCountNo
warningsNo
comparisonNo
diagnosticsNo
totalRowCountNo
reportMetadataNo
ecommerceActivityNo
diagnosticCoverageNo
siteSearchActivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond the annotations: it says the operation is free and defaults to the last 28 complete property days, though it does not discuss pagination or rate limits.

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

Conciseness5/5

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

Three tightly written sentences, front-loaded with the purpose and followed by sibling routing and default behavior. Every sentence earns its place with no redundant restatement of the schema.

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?

For a 13-parameter analytics tool with an output schema and annotations, the definition covers purpose, alternatives, default reporting period and read-only/free behavior. It leaves filter and pagination details to the schema, which is reasonable given the high schema coverage.

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

Parameters3/5

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

Schema description coverage is 85%, so the schema already documents most parameters. The description adds the default date window and organic-only scope, but does not explain filter syntax or parameter interactions beyond what the schema provides. Baseline 3 is appropriate.

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 specific verb and resource: Organic Search landing pages from Google Analytics, including sessions, engagement, key events and ecommerce outcomes. It clearly distinguishes this report from get_landing_page_insights and get_search_opportunities by explaining the different role each tool plays.

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

Usage Guidelines5/5

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

Gives an explicit use case, 'what organic visitors did on the site,' and names two sibling alternatives with the conditions that select them. The routing guidance is specific enough that an agent can choose correctly without opening other schemas.

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