Skip to main content
Glama

Search Console opportunities

search_console_opportunities
Read-only

Surface Search Console opportunities: near-page-one queries that can gain organic clicks, top-5 queries with low click-through rates, and question queries. Read-only, changes nothing.

Instructions

Finds where more organic clicks are within reach: queries on positions 4-20 with the clicks a realistic climb would add, top-5 queries with an unusually low click-through rate (a title or description to fix), and question-shaped queries. Changes nothing.

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": {
      "site_url": "<site_url>"
    },
    "name": "search_console_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending 3 days ago (yesterday with fresh)
freshNoInclude the last 2-3 days, which Google is still filling in (they read low). Use to check something from the last few days
limitNoMost rows in each list
end_dateNoExact last day, YYYY-MM-DD
site_urlYesSearch Console property exactly as search_console_sites lists it, e.g. sc-domain:example.com or https://www.example.com/
start_dateNoExact first day, YYYY-MM-DD
exclude_query_regexNoLeave out queries matching this RE2 regex, typically the brand name, e.g. (?i)acme|ac me

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.46.0
    • changedInput schema / properties / start_date / description
      Previous value: -"Exact first day, YYYY-MM-DD. Pass with end_date to use exact dates instead of days"New value: +"Exact first day, YYYY-MM-DD"
  2. First observedv0.11.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so 'Changes nothing' merely restates them. What the description genuinely adds is the analytical behavior: the position 4-20 band, the estimated clicks a realistic climb would add, the low-CTR-on-top-5 heuristic tied to titles/descriptions, and the question-query shape. It does not cover result size, empty-result behavior, or the data lag.

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?

A single front-loaded sentence with a colon-delimited list of the three opportunity types — dense and waste-free. The trailing 'Changes nothing' is mildly redundant with the read-only annotation and pads an otherwise tight definition.

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?

With no output schema, the description usefully characterizes the shape of the return (three named lists with their selection logic), which is the main gap it needs to fill. It leaves the date-window default and per-list row cap to the schema, which is reasonable given 100% parameter coverage.

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 days, fresh, limit, start_date/end_date, site_url and exclude_query_regex are all already documented with useful detail in the schema. The description adds nothing about any parameter, so the baseline of 3 applies.

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 names a specific verb ('Finds') and resource (organic-click opportunities), and enumerates the three exact opportunity types returned: queries at positions 4-20, top-5 queries with low CTR, and question-shaped queries. That specificity lets an agent distinguish it from raw-report siblings like search_console_performance, though no sibling is named explicitly.

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?

The framing 'where more organic clicks are within reach' implies the diagnostic use case, and the closing 'Changes nothing' hints that acting on findings is a different tool's job (the propose_* family). There is no explicit statement of when to pick this over search_console_performance or summary, and no exclusions, so usage is only implied.

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