Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get AI visibility trend

seo_get_ai_visibility_trend
Read-onlyIdempotent

Answer whether AI visibility is improving or declining. Compares the latest N days with the N days before, using neutral prompts from finished runs, including scheduled and manual runs. A cell is one prompt, engine, collection market and own-brand identity. Each period's brand mention and owned-site citation rate is the mean of cell rates over cells collected in both periods; change is in percentage points. Failed and no-answer collections are coverage, never lost visibility. Read comparison before claiming movement: only comparable reports a change; incomplete (under 90% collection), scope_changed, no_previous and no_data do not. Also returns per-engine rows and one point per run, computed on the matched cells when a comparison exists. Uses no credits.

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_ai_visibility_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLength of each period. Compares the latest N days with the N days before. Defaults to 7, or 90 for a monthly tracker.
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses non-obvious behavior: the comparison is over matched cells only, rates are means of cell rates rather than pooled aggregates, change is expressed in percentage points, and failed/no-answer collections count as coverage rather than lost visibility. It also enumerates the comparability statuses and explains that only 'comparable' reports a change, which prevents a serious misinterpretation, and notes the run consumes no credits.

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 answerable question is front-loaded and nearly every sentence carries real information (comparability rules, matched-cell methodology, no-credit cost). It is dense, though: the sentence defining a cell and the sentence on mean-of-cell-rates are jargon-heavy and slightly harder to parse than needed. Some phrasing, like the failed/no-answer clause, is compact but reads as a list-in-prose.

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 carries the full burden of explaining returns, and it does name the key outputs (comparison status, per-engine rows, one point per run) plus the status vocabulary. What is missing is any indication of the shape or levels of the returned rows (field names, magnitude/scale of rates), so an agent still has to inspect the response. For a two-parameter read tool with full schema coverage, this is close to complete.

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% and the schema already documents siteId, the days enum (7/28/90), and the default (7, or 90 for a monthly tracker). The description restates the period-comparison meaning of days but adds no format, constraint, or edge-case detail beyond the schema. Baseline 3 is appropriate.

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 opens with a specific question-based purpose ("Answer whether AI visibility is improving or declining") and states the mechanism (comparing the latest N days with the prior N). It defines its unit of analysis (a cell = prompt, engine, collection market, own-brand identity) and notes it returns per-engine rows and per-run points, which separates it from result/answer/run siblings. It never names an alternative tool explicitly, so sibling differentiation is inferred rather than stated.

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?

There is strong guidance on how to interpret the output before acting ("Read comparison before claiming movement: only comparable reports a change; incomplete..., scope_changed, no_previous and no_data do not"), plus a cost note ("Uses no credits") that helps an agent decide to call it. However, there is no explicit when-to-use-this-vs-another guidance, e.g., when to use it instead of seo_get_ai_visibility_results or seo_get_ai_visibility_tracker. Usage context is implied rather than routed.

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