Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Console performance report

gsc_search_analytics
Read-onlyIdempotent

Retrieve clicks, impressions, CTR, and position data from Google Search Console, grouped by query, page, country, device, or date, with filters and pagination for targeted analysis.

Instructions

Search performance (clicks, impressions, CTR, position) grouped by query, page, country, device, date or searchAppearance, with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesEnd: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).
filtersNoAll filters are AND-ed.
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
rowLimitNo
startRowNoPagination offset.
dataStateNo'all' includes fresh, not yet final, data. 'hourly_all' is required for (and only works with) the 'hour' dimension, which returns up to the last 10 days broken down by hour: use it to confirm within hours that a republished page or a fixed canonical is being picked up, instead of waiting out the usual 2-3 day lag.final
startDateYesStart: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).
dimensionsNoGroup-by; [] for totals, ['date'] for a trend.
searchTypeNoweb
aggregationTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.10.0
    • changedInput schema / properties / dataState / description
      Previous value: -"'all' includes fresh, not yet final, data."New value: +"'all' includes fresh, not yet final, data. 'hourly_all' is required for (and only works with) the 'hour' dimension, which returns up to the last 10 days broken down by hour: use it to confirm within hours that a republished page or a fixed canonical is being picked up, instead of waiting out the usual 2-3 day lag."
    • changedInput schema / properties / dataState / enum
      Previous value: -[
-  "final",
-  "all"
-]New value: +[
+  "final",
+  "all",
+  "hourly_all"
+]
    • changedInput schema / properties / dimensions / items / enum
      Previous value: -[
-  "query",
-  "page",
-  "country",
-  "device",
-  "date",
-  "searchAppearance"
-]New value: +[
+  "query",
+  "page",
+  "country",
+  "device",
+  "date",
+  "hour",
+  "searchAppearance"
+]
    • changedInput schema / properties / filters / items / properties / dimension / enum
      Previous value: -[
-  "query",
-  "page",
-  "country",
-  "device",
-  "date",
-  "searchAppearance"
-]New value: +[
+  "query",
+  "page",
+  "country",
+  "device",
+  "searchAppearance"
+]
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."New value: +"Search Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites)."
  2. Changed9 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / dataState / description
      Previous value: -"'all' includes fresh (not yet finalized) data of the last days."New value: +"'all' includes fresh, not yet final, data."
    • changedInput schema / properties / dimensions / description
      Previous value: -"Group-by dimensions. Omit for site totals; use ['date'] for a daily trend."New value: +"Group-by; [] for totals, ['date'] for a trend."
    • changedInput schema / properties / endDate / description
      Previous value: -"End date: YYYY-MM-DD, 'today', 'yesterday' or 'NdaysAgo' (e.g. '28daysAgo'). Search Console data lags ~2-3 days."New value: +"End: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days)."
    • removedInput schema / properties / filters / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / filters / items / properties / expression / description
      Previous value: -"Value to match. For device use DESKTOP/MOBILE/TABLET; for country use 3-letter ISO code like 'usa', 'chn'."New value: +"Value; device: DESKTOP/MOBILE/TABLET, country: 3-letter code like 'usa'."
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Property URL exactly as shown in Search Console, e.g. 'https://example.com/' or 'sc-domain:example.com'. Use gsc_list_sites to discover it."New value: +"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."
    • changedInput schema / properties / startDate / description
      Previous value: -"Start date: YYYY-MM-DD, 'today', 'yesterday' or 'NdaysAgo' (e.g. '28daysAgo'). Search Console data lags ~2-3 days."New value: +"Start: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days)."
    • addedInput schema / properties / startRow / maximum
      Added value: +9007199254740991
  3. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds some behavioral context by enumerating returned metrics, grouping, filters, and pagination, but it does not disclose limitations like data lag, sampling, or row-limit behavior beyond what the schema already notes.

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 a single, tight sentence with no filler. Every clause adds value: metrics, grouping dimensions, filters, and pagination are all front-loaded and relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with no output schema and a moderately documented schema, this is functional but thin. It names the core outputs and grouping options, but omits usage context and operational caveats such as data lag and pagination offset behavior, leaving the schema and annotations to carry the rest.

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 70%, so most parameters already carry descriptions. The description's dimension list maps directly to the existing dimensions enum and adds no new semantic detail for rowLimit, searchType, or aggregationType, which remain undocumented in the schema and are not clarified here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the resource ('Search Console performance') and the exact metrics returned: clicks, impressions, CTR, position. It also lists grouping dimensions and mentions filters/pagination, which distinguishes it from sibling GSC inspection tools. It lacks an explicit verb like 'fetch' or 'list', so it is clear but not quite a 5.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus related siblings like gsc_compare_periods, gsc_opportunities, or gsc_ctr_opportunities. It neither states exclusions nor names alternatives, so an agent has to infer placement from the tool name alone.

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

Deploy Server

Other Tools