Skip to main content
Glama
Sign In
GSC SEO MCP

GSC SEO MCP

by samalyxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

advanced_filter_query

Pull up to 50,000 rows of Search Analytics data using advanced dimension filters for deeper SEO audits.

Instructions

Pull up to 50,000 Search Analytics rows with advanced filters for deeper audits.

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": "advanced_filter_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNoGoogle Search Console property URL, e.g. sc-domain:example.com or https://www.example.com/.
startDateNoStart date in YYYY-MM-DD. If omitted, days is used.
endDateNoEnd date in YYYY-MM-DD. If omitted, days is used.
daysNoLookback window when startDate/endDate are omitted.
dimensionsNo
filtersNoSearch Analytics dimension filters. Operators: contains, equals, notContains, notEquals, includingRegex, excludingRegex.
maxRowsNo
searchTypeNoweb
dataStateNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description bears full burden. It mentions the 50,000 row limit but omits key behavioral traits like permissions, performance, return format, or how filters aggregate data. The description is too brief for a complex tool.

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?

The description is a single sentence that front-loads the row limit and filtering capability. It is concise and free of fluff, though it could benefit from additional structure given the tool's complexity.

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

Completeness2/5

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

Given the high parameter count (9), many sibling tools, and no output schema or annotations, the description is incomplete. It lacks details on filter syntax, error handling, and how it differs from similar tools, making it insufficient for effective agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 56%, but the description adds no parameter-level detail beyond the generic 'advanced filters'. It fails to explain the meaning of parameters like dataState or searchType, relying on schema alone, which is insufficient at this coverage.

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 it pulls up to 50,000 rows with advanced filters for deeper audits, specifying the verb and resource. It hints at differentiation from sibling tools like search_analytics but does not explicitly distinguish it.

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 guidance on when to use this tool versus alternatives, such as basic search_analytics. It does not mention exclusions or prerequisites, leaving the agent uninformed about context.

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