Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_ai_visibility_history

Retrieve daily AI-visibility history as chart-ready date/value points showing the percentage of tracked prompts whose answers linked to your brand, plus point count and insufficient-history flags.

Instructions

The daily AI-visibility trend: one series of {date, value} points where value is the percentage of tracked prompts whose answers linked to the brand that day, ready to chart. Also returns the number of points in range and an insufficient_history flag for windows too short to read.

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": "get_ai_visibility_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the return shape ({date, value} points, a point count, and an insufficient_history flag) and warns that short windows are unreadable. However it never states whether the date window is configurable (the schema has zero parameters) or what the default range and timezone are, which is a material omission for a trend tool.

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?

Two sentences, front-loaded with what the tool returns, and every clause adds information (metric definition, point count, caveat flag). The first sentence is dense but not padded; nothing is wasted.

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, so the description correctly explains the returned series, count, and flag, which is the main thing an agent needs. The remaining gap is how the date window is selected given the parameter-less schema, which leaves an agent guessing about scope.

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?

The tool takes zero parameters, so the baseline is 4. Nothing beyond the schema is needed, though the description's references to 'in range' and 'windows too short' raise an unanswered question about where the range comes from.

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 verb (returns the daily AI-visibility trend) plus the resource and the exact metric: percentage of tracked prompts whose answers linked to the brand per day. That metric definition distinguishes it in substance from siblings like get_ai_visibility_mentions and get_ai_visibility_share_of_voice, but it never names those alternatives 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?

Usage is only implied: 'ready to chart' and the daily-series framing signal time-trend use, and the insufficient_history note implies short windows are unsuitable. There is no explicit when-to-use, when-not, or pointer to the sibling that answers a different question (mentions or share of voice).

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

Deploy Server

Other Tools