Skip to main content
Glama
ajmalaksar25

gsc-mcp

by ajmalaksar25

Find SEO opportunities

find_opportunities

Identify striking distance rows (positions 5-20) and high-impression low-CTR pages, returning a ranked list with reasons for each opportunity.

Instructions

Surface actionable wins: 'striking distance' rows ranked between positions 5-20 (small gains can push them to page one) and high-impression / low-CTR rows (the listing shows but few click). Returns a ranked, deduped list with a reason for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window. Default 90.
limitNoOpportunities 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.
dimensionNoAnalyze by query or page. Default query.
minImpressionsNoIgnore rows below this impression count. Default 50.
Behavior4/5

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

With no annotations, the description takes on the full burden. It discloses that the tool returns a 'ranked, deduped list with a reason for each item,' and explains the two opportunity types. This is adequate for a read-only analysis tool.

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 extremely concise (two sentences, ~40 words) and front-loaded with the core value proposition 'Surface actionable wins'. Every word serves a purpose without redundancy.

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 5 parameters, no output schema, and no annotations, the description adequately covers what the tool does and what it returns. It explains the opportunity logic and the nature of the output. Minor improvement could specify prerequisites like Search Console access.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the overall output (ranked, deduped) and the logic behind the opportunities, complementing the parameter-specific schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to surface actionable SEO opportunities. It specifies two concrete categories ('striking distance' and high-impression/low-CTR) and distinguishes it from sibling tools like query_search_analytics, top_pages, or top_queries by focusing on opportunities rather than raw data.

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

Usage Guidelines4/5

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

The description explains when to use the tool by defining the opportunity types (positions 5-20 and high-impression/low-CTR). It implicitly guides usage for finding quick wins, but does not explicitly exclude cases where other tools might be more appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ajmalaksar25/gsc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server