Skip to main content
Glama

AI crawlers

ai_crawlers
Read-onlyIdempotent

Daily AI crawler requests (GPTBot, ClaudeBot, PerplexityBot and others, by self-reported User-Agent) seen by Motif's tracker and collector for one website. UTC days; default the last 28. Not a count of people or prompts.

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

Input Schema

NameRequiredDescriptionDefault
toNoinclusive UTC end YYYY-MM-DD; default today (UTC)
fromNoinclusive UTC start YYYY-MM-DD; default last 28 days
periodNonamed window in UTC days instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the data comes from Motif's tracker and collector, attribution is via self-reported User-Agent (an accuracy caveat), and days are UTC with a default 28-day window. It stops short of describing granularity per bot or latency, but the important caveats are disclosed.

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?

Three compact sentences, front-loaded with what the tool returns and followed by the time semantics and the misuse caveat. Nothing is redundant, though the parenthetical bot list is slightly decorative and the caveat could be paired more tightly with the scope statement.

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?

An output schema exists, so the description need not explain return values, and annotations cover the safety profile. The description fills the remaining gaps that matter: source of the data, self-reported User-Agent caveat, UTC-day granularity, and default window. Only the interaction between the from/to and period parameters is left implicit.

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?

All four parameters already carry full schema descriptions, including formats, defaults and the period enum values, so the schema does the heavy lifting. The description reinforces the UTC-day semantics and the 28-day default, but adds no syntax or interaction detail (for example, from/to versus period precedence) beyond what the schema states.

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?

The description names a specific data resource (daily AI crawler requests by self-reported User-Agent, covering GPTBot, ClaudeBot, PerplexityBot and others) and scopes it to one website for a UTC window. The closing 'Not a count of people or prompts' explicitly separates it from human-traffic metrics so an agent can distinguish it from analytics-style siblings.

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?

It gives clear framing on what the data represents and warns against misreading it as human traffic, which is a useful exclusion for interpretation. However, it never names an alternative tool or states a concrete condition under which an agent should pick this over analytics_snapshot, insights, or tracking_status.

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