Skip to main content
Glama

Get real AI crawler visits

get_crawler_activity
Read-onlyIdempotent

Real AI crawler visits to the member's site from Kliqo's Crawl insights (Cloudflare connection): visits by crawler (verified by IP), errors they hit, the pages they read most and whether AI answers cite them, and visitors sent by AI assistants. Says so when Crawl insights isn't connected. Use for "is ChatGPT crawling our site?" or "which pages do AI bots read?". Needs sign-in to Kliqo (read-only).

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

Input Schema

NameRequiredDescriptionDefault
rangeNo30d
projectNoProject name, domain or id; leave out for the workspace's current project

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it adds real behavioral context: sign-in to Kliqo is required, output is read-only, and the tool self-reports the degraded state when Crawl insights isn't connected. Provenance (IP-verified) also tells the agent how much to trust the numbers. Missing only rate/limit or caching behavior.

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-loaded with what the tool returns, then the fallback behavior, then trigger examples and the auth note — a sensible ordering with no filler. The first clause is long and comma-stacked, but every item in it is a distinct data category the agent needs.

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 an output schema present the description needn't explain return shapes, and it correctly spends its words on auth, data source, and the disconnected-Crawl-insights case. The only substantive hole is the unexplained 'range' parameter against a 2-param, no-required-fields interface.

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 50% — 'project' is documented in the schema, while 'range' appears as a bare enum with a default. The description says nothing about the time window, the accepted values, or the 30d default, so it adds no meaning over the structured fields and leaves the most likely-to-be-set parameter to the schema alone.

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 (real AI crawler visits) plus the data source (Kliqo Crawl insights via Cloudflare), and enumerates the exact payload: visits by crawler IP-verified, errors, top pages, AI-answer citations, and assistant referrals. An agent can distinguish this from list_ai_crawlers or verify_crawler_ip without opening the schema.

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?

Gives two concrete trigger questions ("is ChatGPT crawling our site?", "which pages do AI bots read?") that map cleanly onto the tool's scope. It does not name the neighboring alternatives (check_ai_crawlers, list_ai_crawlers) or state when not to use it, so routing still requires a guess when the agent's intent is ambiguous.

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