Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by ajmalaksar25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Top queries

top_queries

Retrieve top search queries for your site ranked by clicks, with configurable date range and result limit.

Instructions

Quick view of the top search queries for a site over the last N days, ranked by clicks.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window. Default 28.
limitNoRows to return. Default 25.
siteUrlNoProperty as shown in Search Console: a URL-prefix property ends with a slash (e.g. "https://example.com/") or a domain property uses "sc-domain:example.com". May be a registered alias, or omitted to use the active/default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should fully convey behavior. It mentions ranking by clicks and a lookback window but omits details like default sorting, pagination behavior, how missing data is handled, or output structure. This leaves significant gaps for the agent.

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, concise sentence (15 words) that efficiently states the tool's purpose. While brief, it avoids fluff. A slightly more structured format (e.g., listing key aspects) could improve scanability.

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 three parameters, no output schema, and no annotations, the description is too sparse to fully define the tool's behavior. It lacks detail on what 'top' means (e.g., by clicks only?), result ordering, and edge cases, leaving the agent underinformed.

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?

All parameters are fully described in the input schema (100% coverage), establishing a baseline of 3. The description adds no additional context beyond schema descriptions, such as data formats or usage tips.

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 provides a quick view of top search queries ranked by clicks over a period. However, it does not explicitly differentiate from sibling tools like query_search_analytics, which may offer similar but more detailed functionality.

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?

No guidance on when to use this tool versus alternatives (e.g., query_search_analytics, compare_periods). The description implies a quick overview but does not outline when a more detailed tool is needed or provide exclusion criteria.

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