Skip to main content
Glama
Sign In

invisit

by dev.invisit
OverviewDiscussionsAdmin

Google search queries

get_search_queries
Read-onlyIdempotent

The Google searches a site appeared for, from its connected Search Console: clicks, impressions, CTR and average position, for the whole site or one page. Google hides rare queries, so totals run low, and its last 2 to 3 days are still settling. For the visits themselves 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_search_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, inclusive, YYYY-MM-DD; default today
fromNoFirst day, YYYY-MM-DD; overrides period
pageNoOne path, such as /pricing
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.2/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent read. The description adds genuinely non-obvious behavioral context the annotations cannot convey: Google suppresses rare queries so totals understate reality, and the most recent 2–3 days are still settling and will shift. That is exactly the kind of caveat an agent needs to avoid misreporting numbers.

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 sentences, front-loaded with what is returned, then data-quality caveats, then the sibling pointer. No sentence is redundant, and the caveats are placed after the core purpose rather than buried.

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?

No output schema exists, so the description carries the burden of explaining return values, and it does so by naming the four metric columns. Row ordering and default limit behavior are left to the schema. A note on ordering or result volume would close the remaining gap.

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 coverage is 100%, so date ranges, period enum, limit and timezone are fully documented in structured fields; baseline is 3. The description adds only a light gloss on scope ('whole site or one page') and implicitly warns that recent days are unreliable, but contributes no syntax or precedence detail beyond the schema.

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?

Names the specific resource (Google searches a site appeared for, sourced from Search Console) and enumerates the returned metrics: clicks, impressions, CTR, average position. Scope is stated ('whole site or one page'), and the final clause distinguishes it from get_breakdown, which covers visits rather than queries.

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?

Explicitly routes the agent to get_breakdown when the user wants visit data instead of query data, which is the main confusion risk among the many sibling report tools. There is no guidance on when the page-scoped return is preferable to the site-wide one, but the invocation context is otherwise clear.

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