Skip to main content
Glama

Visibility Genies

Read AI crawler visits

get_ai_crawler_visits
Read-only

Reads the AI crawler visits saved for a project: hits per day per crawler (ChatGPT, Claude, Perplexity, Common Crawl and others), split into verified (the address is in the list the crawler's operator publishes) and name only, the requests the site refused (401, 402, 403 or 429), each crawler's last visit, and its most fetched pages. Visits come from the project's connected Cloudflare zone, read every day, or from server logs uploaded on the AI crawler visits page; source picks one, and the default is Cloudflare when it holds visits. Free: reads saved data. Connecting and uploading happen on the page only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays of visits, counted back from the newest day of the chosen source (default 30).
sourceNocloudflare for the visits read from the connected Cloudflare zone, logs for uploaded server logs. Default: cloudflare when it holds visits, else logs.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
countsYes
sourceYes
crawlersYes
topPagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond that: data provenance (Cloudflare zone read daily vs uploaded server logs), that it is free and reads saved data, and that no connection/upload can be performed through the 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?

Front-loads the resource and its contents, then the provenance and constraints. It is dense and somewhat run-on in the middle, but every clause carries information and nothing is redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 spelled out, yet the description still summarizes what the payload contains. Combined with the source/default rules and the free/read-only framing, an agent has everything needed to call it 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 coverage is 100%, so all three parameters are already documented, including the source default and the days default. The description restates the source default and adds only the nuance that days are counted back from the newest day of the chosen source, which is marginal over the schema.

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?

States a specific verb and resource ("Reads the AI crawler visits saved for a project") and enumerates the exact content returned: hits per day per crawler, verified vs name-only split, refused requests, last visit, top pages. No sibling covers crawler visits, so the agent can distinguish it immediately.

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?

Explains the source selection rule ("source picks one, and the default is Cloudflare when it holds visits") and clarifies that connecting/uploading happen on the page only, so the agent knows not to attempt setup here. It lacks an explicit when-to-use-vs-alternative statement, but the scope is clear.

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