Skip to main content
Glama
Sign In

invisit

by dev.invisit
OverviewDiscussionsAdmin

Google Discover pages

get_discover_pages
Read-onlyIdempotent

The pages Google showed in Discover, from a connected Search Console: impressions, clicks and CTR, most shown first, with Google Web search clicks for comparison. Google reports no queries or positions for Discover, only reports it for properties past a minimum of impressions, and its last 2 to 3 days are still settling. For what visitors did on a page use get_breakdown.

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": {
      "site_id": "<site_id>"
    },
    "name": "get_discover_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, inclusive, YYYY-MM-DD; default today
fromNoFirst day, YYYY-MM-DD; overrides period
pageNoOne path, such as /news/some-story
limitNoRows to return, at most 100
periodNoWindow ending now; days are whole days in the timezone. Ignored when from is set.30d
site_idYessite_id from list_sites; a site name, slug or domain also resolves
timezoneNoIANA zone for day boundaries; default the user's

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only / idempotent / non-destructive annotations, the description discloses substantial behavior: rows are ordered most-shown first, Google reports no queries or positions for Discover, results only exist past a minimum impressions threshold, and the last 2-3 days are still settling. These are exactly the caveats an agent needs to interpret or trust the output.

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?

Purpose and metrics are front-loaded in the first clause, and the remaining sentences each carry a distinct caveat (no queries/positions, minimum impressions, settling data, sibling routing). It is dense and slightly long-winded, but essentially no sentence is filler.

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 no output schema, the description must explain returns itself, and it does: row content, ordering, comparison metrics, and data-freshness caveats. For a seven-parameter read tool with full schema coverage and clear annotations, nothing material is missing.

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 every parameter (from/to/period/limit/page/timezone/site_id) is already documented in the schema. The description adds no format, default, or precedence detail beyond what is structured, so baseline 3 applies; the "most shown first" ordering note is behavioral rather than parameter semantics.

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 names a specific resource (pages Google showed in Discover from a connected Search Console) and the exact metrics returned (impressions, clicks, CTR, plus Web search clicks for comparison). It is clearly distinguishable from siblings like get_search_queries or get_overview without opening any schema.

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 an explicit alternative with its selecting condition: "For what visitors did on a page use get_breakdown." It also implies that query/position-level questions are out of scope for this tool, though it does not name the sibling that would answer them or state exclusions such as properties below the impressions minimum.

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

All invisit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources