Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by ajmalaksar25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Top pages

top_pages

View top landing pages ranked by clicks for any Google Search Console property over a configurable lookback window.

Instructions

Quick view of the top landing pages 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_pages"
  }
}

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

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention authentication requirements, rate limits, or whether the tool is read-only. The description only states it's a 'quick view', leaving important safety and usage context unaddressed.

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?

A single 18-word sentence that is front-loaded with the purpose. No redundant words; every word contributes to understanding.

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 simple tool with three parameters and no output schema, the description is adequate but incomplete. It does not hint at the return structure (e.g., list of pages with click counts) or clarify edge cases like empty results.

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 100%, so the schema already documents all three parameters. The description adds that results are 'ranked by clicks', which is extra context, but does not provide new meaning beyond the schema.

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 tool retrieves top landing pages over a time period ranked by clicks. It distinguishes from siblings like 'top_queries' (queries vs pages) and 'query_search_analytics' (more detailed vs quick view), but does not explicitly name alternatives.

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

Usage Guidelines3/5

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

Implied usage is for a quick overview of top pages by clicks, but there is no guidance on when to use alternatives like 'query_search_analytics' for more detail or filtering, nor when not to use this tool.

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