Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Question queries (AI Overview / featured snippet targets)

gsc_question_queries
Read-onlyIdempotent

Find question-style queries your site gets impressions for, grouped by page, and check each page for matching headings and FAQ schema to target FAQ sections and AI Overviews.

Instructions

What to add to a page, not which page to fix. Question-style queries (how/what/why/best, cómo/qué/cuánto...) the site gets impressions for, grouped by page; optionally checks whether each page has a matching heading and FAQPage schema. Targets for FAQ sections and AI Overviews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
endDateNoEnd: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).3daysAgo
filtersNoScope the analysis, e.g. page contains '/es/' for one language folder. Defaults to the whole property.
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
startDateNoStart: YYYY-MM-DD, today, yesterday or NdaysAgo (data lags 2-3 days).90daysAgo
checkPagesNoHow many of the top pages to fetch and check for matching headings / FAQ schema (0 = skip).
searchTypeNoweb
minImpressionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / filters
      Added value: +{
+  "description": "Scope the analysis, e.g. page contains '/es/' for one language folder. Defaults to the whole property.",
+  "items": {
+    "properties": {
+      "dimension": {
+        "enum": [
+          "query",
+          "page",
+          "country",
+          "device",
+          "searchAppearance"
+        ],
+        "type": "string"
+      },
+      "expression": {
+        "description": "Value; device: DESKTOP/MOBILE/TABLET, country: 3-letter code like 'usa'.",
+        "type": "string"
+      },
+      "operator": {
+        "default": "equals",
+        "enum": [
+          "equals",
+          "notEquals",
+          "contains",
+          "notContains",
+          "includingRegex",
+          "excludingRegex"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "dimension",
+      "expression"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / searchType
      Added value: +{
+  "default": "web",
+  "enum": [
+    "web",
+    "image",
+    "video",
+    "news",
+    "discover",
+    "googleNews"
+  ],
+  "type": "string"
+}
    • 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. Changed5 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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)."
    • addedInput schema / properties / minImpressions / maximum
      Added value: +9007199254740991
    • 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)."
  3. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds behavioral details about grouping by page and optional checks for headings/FAQ schema, which are not in annotations. It does not contradict annotations and adds meaningful context about what the tool does with the data.

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, front-loaded sentence that immediately conveys the core purpose and differentiator. Every part adds value – examples of query types, grouping behavior, optional check, and target use case. No wasted words.

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 read-only analysis tool with 8 parameters and no output schema, the description sufficiently explains the tool's purpose and output concept (grouped queries per page, optional schema checks). Operational details like date ranges, filters, and thresholds are covered in the schema. Given the complexity and annotations, this is largely complete, though it does not describe return format or potential limitations.

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 63%, with descriptions for endDate, startDate, siteUrl, filters, and checkPages. The description adds value by explaining the purpose of checkPages (checking headings/FAQ schema) and the grouping behavior, but it does not clarify top, minImpressions, or searchType beyond the schema. It does not fully compensate for the uncovered parameters.

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 clearly states the tool's purpose: it identifies question-style queries (with examples) and groups them by page, with an optional check for matching headings and FAQ schema. It explicitly distinguishes itself from sibling tools by saying 'not which page to fix', which differentiates it from page-audit or fix-oriented tools.

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?

The description provides usage context by stating 'What to add to a page, not which page to fix' and mentions 'Targets for FAQ sections and AI Overviews', implying when to use it. However, it does not explicitly name alternative tools or provide explicit when/when-not conditions beyond this contrast.

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