Skip to main content
Glama

GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP

Live Google top results

serp_top_results
Read-only

Live Google SERP for query. Returns the top N organic results plus a summary of which SERP features are present (Knowledge Panel, Map Pack, Featured Snippet, People Also Ask, related searches). AI Overview is not measured (always null), and for some countries (seen for "tr") no features come back at all: then features.feature_data_available is false and the fields are null.

Use this when GSC tells you the position but you also need to know WHO is ranking above you, or whether Map Pack / Shopping / Featured Snippet are eating clicks despite a stable position.

Input Schema

NameRequiredDescriptionDefault
numNonumber of organic results, 1..100 (default 10).
queryYesGoogle search query.
deviceNo"desktop" or "mobile". Different SERP features per device.desktop
countryNoISO 3166 country code (us, tr, de, ...). SERPs differ per country - use the country your real users search from.tr
languageNoISO 639 language code (en, tr, de, ...).en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

It discloses critical behavioral edge cases not in the schema, such as AI Overviews always being null and country-specific limitations (e.g., 'tr') regarding feature availability and the use of 'feature_data_available' flag.

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 highly informative and well-structured, leading with capabilities before detailing constraints. It is slightly verbose, but the density of information justifies the slight reduction from 5.

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?

Given the complexity of SERPs and the presence of localized behavior, the description is exceptionally complete. It addresses output limitations (AI Overview) and regional variations that an agent must know to use the tool effectively.

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?

Although schema coverage is 100%, the description adds vital context regarding the 'country' parameter, advising the user to select the country corresponding to their actual user base due to SERP differences.

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 clearly states the tool retrieves live SERPs and goes beyond simple link retrieval by auditing specific SERP features like Knowledge Panels and Map Packs.

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?

It provides an explicit use case scenario: use the tool when GSC position data is insufficient and the agent needs context on competitor presence or feature interference.

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.