Skip to main content
Glama

Visibility Genies

Read landing page insights

get_landing_page_insights
Read-only

Organic Traffic Insights: use it to see each landing page's search results and site results side by side. One row per landing page with Search Console clicks, impressions, CTR (0-1) and average position beside Google Analytics organic sessions, engaged sessions, engagement rate (0-1) and key events for the same period, plus the previous period's clicks and sessions. Pages match on host and path (scheme, a leading www., trailing slash, query string and fragment ignored). A null means that source has no row for the page, not zero; a side that is not connected is reported with a link and leaves the other side's rows in place. Rows are sorted by clicks, then sessions. For the queries behind a page, call get_search_console_performance with dimensions ['query'] and a page equals filter on each of its searchConsoleUrls. get_search_opportunities picks the pages closest to winning more clicks instead, and get_google_analytics_organic_landing_pages gives Analytics outcomes alone, with ecommerce. Read only and free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 100, max 1000).
deviceNoOnly this device: desktop, mobile or tablet. Applies to both sources.
offsetNoRows to skip, to page through them (default 0).
countryNoOnly this country, as its two-letter ISO code, for example DE. Applies to both sources.
endDateNoExplicit end (YYYY-MM-DD). Use with startDate.
dateRangeNoThe Traffic Insights page's periods (default last_28_days), ending ~3 days back for Search Console's lag. Ignored when startDate and endDate are given.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoExplicit start (YYYY-MM-DD). Use with endDate.
pageContainsNoOnly pages whose address contains this text, in any case. Applies to both sources.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
rowsNo
periodNo
reasonNo
hasMoreNo
rowCountNo
nextOffsetNo
searchConsoleNo
totalRowCountNo
previousPeriodNo
googleAnalyticsNo

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?

Annotations already cover the safety profile (readOnly, non-destructive, closed world), but the description adds substantial non-obvious behavior: null means the source has no row rather than zero, a disconnected source is reported with a link while the other side's rows remain, page matching is on host and path ignoring scheme/www/trailing slash/query/fragment, and rows are sorted by clicks then sessions. That is real value beyond the annotations, though it does not cover failure modes or partial-response edge cases in more depth.

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 purpose and payload shape, then matching semantics, then sibling routing — a sensible order. It is dense and long, but nearly every sentence carries distinct information (null semantics, matching rules, sort order, alternatives); no filler or restatement of the title.

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?

An output schema exists, yet the description still names the returned columns and their units (CTR 0-1, engagement rate 0-1), which is helpful for interpreting rows rather than redundant. Combined with matching rules, null/disconnected-source handling, sort order and explicit sibling alternatives, an agent has everything needed to call and read this tool correctly.

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 100%, so the schema already documents limit, offset, device, country, dateRange, startDate/endDate and projectId, including the default period and the ~3 day Search Console lag. The description adds only indirect meaning — that both sides cover 'the same period' plus a previous comparison period — without per-parameter guidance beyond the schema. 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 ('see each landing page's search results and site results side by side') and immediately frames the payload as one row per landing page with named Search Console and Analytics metrics. This is clearly distinguishable from the sibling Analytics-only and Search Console-only tools named later.

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?

Explicitly routes the agent: use get_search_console_performance with dimensions ['query'] plus a page equals filter for the queries behind a page, get_search_opportunities when the goal is pages closest to winning more clicks, and get_google_analytics_organic_landing_pages when Analytics outcomes with ecommerce suffice. When-to-use and when-to-use-something-else are both stated.

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