Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get Google Search Console performance

seo_get_search_console_performance
Read-onlyIdempotent

Query the connected Search Console property's Search Analytics: clicks, impressions, CTR, and average position by query/page/country/device/date. First-party data — use it for what already ranks, near-ranking queries, and pages with real demand. Google sorts by clicks and can't filter by position, so minPosition/maxPosition/minImpressions are applied server-side over the top 1000 rows of the window — use them instead of fetching everything. ctr is a 0-1 fraction; position is a 1-based average and is omitted from rows when type is 'discover' or 'googleNews' (Google does not report it there — treat it as unavailable, not a failure); dates are Pacific Time; the last ~3 days may be incomplete. Reads only the Search Console property already connected to an Sextant project the caller is authorized to access. The server selects the Google account and property from that project's saved connection. Read-only; uses no credits. It calls one fixed endpoint of the Sextant SEO API (https://sextantweb.com/docs/ai): filters hold only the fields in its schema.

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": {
      "siteId": "<siteId>"
    },
    "name": "seo_get_search_console_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoSearch type (default web).
siteIdYesThe Sextant site ID.
endDateNoExplicit end (YYYY-MM-DD, Pacific Time). Use with startDate.
filtersNoAND-combined filters. To get the queries for one page: [{dimension:'page',operator:'equals',expression:'https://example.com/post'}] with dimensions ['query'].
rowLimitNoRows per call (default 250, max 1000). GSC sorts by clicks desc; paginate with startRow when hasMore is true.
startRowNoPagination offset.
dataStateNo'all' (default) includes fresh/incomplete recent data.
dateRangeNoConvenience window (default last_28_days). End is set ~3 days back for GSC data lag. Ignored if startDate+endDate are given. Max lookback is 16 months.
startDateNoExplicit start (YYYY-MM-DD, Pacific Time). Use with endDate.
dimensionsNoGroup rows by these dimensions. Default ['query']. Use ['page'] for top pages, ['query','page'] to map queries to pages / spot cannibalization, ['date'] for a time series.
maxPositionNoKeep rows with average position <= this.
minPositionNoKeep rows with average position >= this. For 'striking distance' queries use minPosition 5, maxPosition 20, minImpressions 50.
minImpressionsNoKeep rows with at least this many impressions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses non-obvious behavior: Google sorts by clicks and cannot filter by position, so position/impression filters run server-side over only the top 1000 rows of the window. It also explains auth/property resolution, that no credits are consumed, that ctr is a 0-1 fraction, that position is a 1-based average omitted for discover/googleNews (an absence, not an error), and that dates are Pacific Time with the last ~3 days possibly incomplete.

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?

Dense but front-loaded: purpose first, then usage, then gotchas. Nearly every clause carries operational weight, though the trailing sentence about calling one fixed endpoint and the docs URL adds little for tool selection and could be trimmed.

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 a 13-parameter tool with no output schema, it covers the important ground: what metrics come back, the grouping behavior, the filtering limitation, and data freshness. It stops short of describing the response envelope (rows array, hasMore) that an agent needs to paginate correctly, though hasMore is at least referenced in the schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: the top-1000-row server-side filtering caveat that determines whether minPosition/maxPosition/minImpressions are trustworthy, plus the ctr/position units and the discover/googleNews omission. It does not add detail about rowLimit/startRow pagination or dataState beyond what the schema already says.

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 opening sentence names a specific verb ('Query') and a precise resource ('Search Console property's Search Analytics'), then enumerates the returned metrics and the available breakdowns (query/page/country/device/date). It also frames the data as first-party GSC data, which distinguishes it from the audit/rank-tracker/AI-visibility siblings.

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 concrete positive guidance ('use it for what already ranks, near-ranking queries, and pages with real demand') and an explicit recipe for the common case ('striking distance' with minPosition 5, maxPosition 20, minImpressions 50). It does not name an alternative tool or state when not to use this one, which keeps it below a 5.

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