Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by ajmalaksar25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Account overview (all sites)

account_overview

Aggregate and rank last-28-day clicks and impressions across all accessible properties for a portfolio overview.

Instructions

Portfolio view across every accessible property: last-28-day clicks and impressions per site, ranked. (Per-site SEO/coverage scores are added in a later phase.)

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window. Default 28.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the data returned (clicks, impressions, ranking) and notes that SEO/coverage scores are added later, which is helpful. However, it does not mention auth requirements, rate limits, or whether the operation is read-only, which are gaps.

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 two sentences, front-loading the core purpose in the first sentence and adding a future note in parentheses. Every word earns its place, with no redundancy or waste.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description provides adequate context about what the tool returns. It lacks details on output format or pagination, but for a ranked overview tool, this is sufficient.

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?

The schema has 100% coverage for the single parameter 'days', including a description. The tool description does not add any additional meaning or constraints beyond what the schema already provides, so baseline 3 is appropriate.

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 portfolio view across all accessible properties, showing clicks and impressions per site ranked for the last 28 days. While it identifies the resource and action, it does not explicitly differentiate from sibling tools like list_sites or top_pages, which also provide site-level data.

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 implies use for a high-level overview but provides no explicit guidance on when to use this tool versus alternatives. No conditions, exclusions, or when-not-to-use are mentioned, leaving the agent to infer usage 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