Skip to main content
Glama

Visibility Genies

Find search opportunities

get_search_opportunities
Read-only

Pages behind Search Console striking-distance queries (the best page for the query ranks 5 to 20, read from up to 25,000 query and page rows), joined with Google Analytics organic landing-page outcomes and scored by demand, business value and reachability: use it to pick the pages worth improving first. Counts are pages, except gscRowsConsidered. Read only and free.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_search_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.

Output Schema

NameRequiredDescriptionDefault
rowsNo
errorNo
quotaNo
sourceNo
statusYes
requestNo
scoringNo
coverageNo
rowCountNo
warningsNo
truncatedNo
reportMetadataNo
totalCandidatePagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered; the description adds cost ("free"), the data sources and the 25,000 query/page row ceiling. It also clarifies an unusual counting convention ("Counts are pages, except gscRowsConsidered"), which is real behavioral information an agent would otherwise misread. It stops short of describing ordering of results or how scoring weights are combined.

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?

The resource and scope are front-loaded in the first clause, with the scoring model and counting caveat following in a tight second sentence. It is dense but nearly every clause carries information; the only slightly redundant bit is "Read only and free" re-stating the readOnlyHint.

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?

An output schema exists, so return values need not be explained, and the description supplies the pipeline, the row cap, the ranking band, the scoring dimensions and the counting units. The main remaining gap is result ordering and how limit interacts with scoring — useful but not essential given the output schema.

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 coverage is 75% and the schema itself already documents projectId, the paired startDate/endDate rule, and the default of the last 28 complete property days. The description adds no parameter-level detail of its own — notably it says nothing about the limit parameter or result ordering — so it sits at the baseline.

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 names a specific, distinctive resource: pages ranking 5–20 for Search Console queries, enriched with GA organic landing-page outcomes and scored. It is clearly not a raw performance report, so an agent can tell it apart from get_search_console_performance without opening either schema.

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?

"use it to pick the pages worth improving first" gives a clear selection context for prioritization work. There are no explicit exclusions or named alternatives (e.g. when to prefer get_search_console_performance for raw query data), which keeps it short of a 5.

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.

Resources