Hexagon MCP

Overview Schema Source Related Servers Discussions Admin

gsc_query

Query Google Search Console performance data read-only to analyze clicks, impressions, CTR, and position by queries, pages, dates, and filters across one or all properties.

Instructions

Query Google Search Console performance data (read-only). Defaults to queries and pages for the last 7 days ending yesterday, with clicks, impressions, CTR and position. Covers one property, or every property the account can access when siteUrl is 'all' or omitted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsc_query"
  }
}

Input Schema

Name	Required	Description
`endDate`	No	YYYY-MM-DD. Default: yesterday.
`filters`	No	Optional dimension filters, all combined with AND.
`siteUrl`	No	One property exactly as in Search Console (sc-domain:example.com or https://example.com/), or 'all' for every verified property. Default: GSC_SITE_URL from .env if set, otherwise all.
`rowLimit`	No	Rows per property. Default 25.
`dataState`	No	'all' includes fresh, not yet final data (default). 'final' is confirmed data only.
`startDate`	No	YYYY-MM-DD. Default: 7 days ago.
`dimensions`	No	Default: ['query','page']. Use ['date'] for a daily trend.
`searchType`	No	Default: web.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully states that the tool is read-only and describes default date/dimension/scope behavior. However, it does not disclose authentication requirements, quotas/rate limits, pagination behavior, or freshness nuances beyond what the schema already says.

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?

The description is two tightly written sentences with no wasted text. It is front-loaded with the core action and then gives defaults and scope efficiently.

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 an eight-parameter query tool with no output schema, the description covers purpose, read-only status, default date range, dimensions, metrics, and multi-property scope. It is not fully complete because it omits return-shape guidance and explicit routing versus sibling analytics tools.

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 all eight parameters. The description consolidates some defaults and explains the siteUrl='all' scope, but does not add parameter semantics 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?

The description names a specific verb and resource: query Google Search Console performance data. It also states read-only behavior and default dimensions/metrics, making it clearly distinguishable from sibling reporting tools such as ga4_report and adsense_report.

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

Usage Guidelines3/5

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

Usage is implied by the resource name and defaults, but the description does not explicitly say when to use this tool instead of ga4_report, adsense_report, or other siblings. It also omits prerequisites or exclusions for selecting this tool.

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

Deploy Server