Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get search opportunities

seo_get_search_opportunities
Read-onlyIdempotent

Pages that rank in Google positions 4 to 20 (Google Search Console), ranked by how much a push could bring: demand (impressions), reachability (how close the page is to the top 3) and business value (visits that start on that page in Sextant analytics). Free; needs Search Console. Dates are days in Pacific Time, as Search Console reports them; leave them out for the 28 days that end 3 days ago (Google needs about 3 days to finish its data). Pages Sextant has no visits for stay in the list, unscored.

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": {
      "siteId": "<siteId>"
    },
    "name": "seo_get_search_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPages to return, 1 to 100. Defaults to 50.
siteIdYesThe Sextant site ID.
endDateNoLast day (YYYY-MM-DD, Pacific Time), included.
startDateNoFirst day (YYYY-MM-DD, Pacific Time), with endDate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The annotations already declare a safe, idempotent, closed-world read, and the description still adds substantial context beyond them: it is free, requires Search Console, dates are Pacific-Time days, omitting dates yields the 28 days ending three days ago because Google needs ~3 days to finalize data, and pages with no Sextant visits remain listed but unscored. These are exactly the operational traits an agent cannot get from the structured fields.

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?

What it returns and how it is ranked come first, followed by cost/prerequisite, then date defaults, then the unscored edge case — a sensible front-loading order with no filler sentences. The ranking clause is a dense mid-sentence run of three bundled factors that takes a second pass to parse.

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?

For a read-only ranked-list tool with no output schema, the definition covers selection criteria, ordering logic, date defaults, prerequisites and the edge case of unscored pages. It does not describe the shape of a returned entry (e.g. whether the individual score components are exposed), which is the one thing an agent might still need to know before formatting results.

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 schema already documents each parameter; the baseline would be 3. The description earns above that by explaining the meaning of the date pair (Pacific Time days, must be used together, and the specific default window when omitted) and why the lag exists. Limit and siteId get no added meaning, which keeps it from a 5.

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 defines the resource precisely: pages ranking in Google positions 4–20 from Search Console, ordered by a composite of demand, reachability and business value. That is far more specific than the title and implicitly separates it from a general performance report. It stops short of naming any sibling tool, so an agent must infer the boundary rather than being told it.

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?

Prerequisites and cost are stated clearly ("Free; needs Search Console"), and the default date window tells the agent it can call with only siteId. However, there is no when-not guidance and no pointer to an alternative such as a broader Search Console performance tool, so the agent gets context but no routing rules.

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