Skip to main content
Glama

MetricPort

Quick wins (striking distance)

gsc_quick_wins
Read-onlyIdempotent

Queries ranking in striking distance (default positions 5-20) with real impressions, ranked by estimated extra clicks if pushed up ~3 positions. Includes the ranking page so you know what to optimize.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property": "<property>"
    },
    "name": "gsc_quick_wins"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
propertyYesSearch Console property id from list_properties, e.g. sc-domain:example.com or https://www.example.com/
maxPositionNo
minPositionNo
excludePatternNoRegex of queries to ignore, e.g. your brand name
minImpressionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description goes further by explaining the ranking heuristic (~3 position lift estimate), the default position window, and that the ranking page is returned — genuinely useful behavioral context beyond the annotations.

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?

Two dense sentences with zero filler. The core purpose (striking-distance queries) leads, followed by the ranking method and the payload content — a well front-loaded structure.

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?

There is no output schema, yet the description explicitly characterizes the return set (queries with real impressions, ranked, with ranking page). That covers the output gap well for a read-only analytics tool, leaving only the under-documented input parameters as a residual gap.

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 only 29% (7 params, only property and excludePattern documented), so the description must carry more weight. It partially compensates by specifying the default position window (5-20), the impressions requirement, and the position-lift heuristic, but days, limit, and the minImpressions threshold semantics remain unexplained.

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 states a specific concept (queries in striking distance, default positions 5-20), the ranking basis (estimated extra clicks if pushed ~3 positions), and what is included (the ranking page). It is clearly distinct from gsc_top_queries or gsc_search_analytics, though it never names the closest sibling (gsc_ctr_opportunities) to sharpen the boundary.

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?

Usage is implied by the concept itself — an agent can infer this is for finding optimizable queries. However, there is no explicit when-to-use, when-not-to-use, or alternative (e.g. gsc_ctr_opportunities) named, so the guidance remains inferential rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.