Skip to main content
Glama
Sign In

Seonix

by io.github.pahaa97
OverviewDiscussionsAdmin

Striking-distance opportunities

gsc_opportunities
Read-onlyIdempotent

Keywords already ranking in a position band (default 4–20) with impressions, ordered by the traffic Seonix estimates they would bring at the target position. The classic striking-distance list: refresh those pages first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsc_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow length (default 28, 7–90).
limitNoRows to return (default 30, max 200).
project_idNoProject id or slug.
max_positionNoUpper bound of the position band (default 20).
min_positionNoLower bound of the position band (default 4).

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 readOnly/idempotent/destructive=false, so the safety profile is covered. The description still adds non-obvious behavior: results are ordered by projected traffic at the target position, and the position band is configurable with a stated default. It omits pagination/tie-breaking or whether near-zero-impression rows are filtered.

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 sentences, front-loaded with what the tool returns and how it is ordered, then a short actionable cue. No filler or 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?

There is no output schema, and the description does disclose the key output dimensions (position, impressions, estimated traffic) and ordering. A bit more on what row fields are returned or on empty-band behavior would fully close the gap, but it is sufficient to call correctly.

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 each of the 5 parameters is already documented with types and defaults. The description only echoes the default band (4–20) and adds no syntax or constraint detail beyond what the schema carries, so baseline 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?

States a specific resource (keywords in a position band) plus a concrete ordering rule (estimated traffic at the target position), which is more than a restatement of the name. It does not explicitly contrast with sibling GSC tools like gsc_top_queries or gsc_impact, so the agent must infer 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?

The closing line 'refresh those pages first' implies a workflow use case, and 'default 4–20' hints at the classic striking-distance scenario. However, no explicit when-to-use/when-not or alternative-tool routing is given among the many gsc_* siblings.

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

All Seonix toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources