Skip to main content
Glama

Get AI bot traffic (who reads the site)

get_ai_traffic
Read-onlyIdempotent

Shows which AI bots read one site: visits from ChatGPT (OpenAI), Claude (Anthropic), Perplexity, Meta, Amazon and others, verified by Cloudflare, with change vs the previous period. On Hostilo PRO also per-bot counts, most read pages, formats (HTML, Markdown, llms.txt, robots.txt) and countries, for 7, 30 or 90 days. Free accounts get the last 7 days: total and operator names. Requests from programs pretending to be AI bots are not counted.

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": {
      "site": "<site>"
    },
    "name": "get_ai_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPeriod length in days (PRO). Free accounts always get 7.
siteYesSite id or name, e.g. "my-portfolio" or "my-portfolio.hostilo.page" (from list_sites).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by disclosing data provenance (verified by Cloudflare), a filtering rule (spoofed bot requests are not counted), and tier-gated response content. It stops short of pagination or rate-limit details, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with what the tool returns, then expanding into PRO/free differences and an exclusion note. Every sentence carries information an agent would otherwise have to guess.

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?

No output schema exists, so the description must describe return content, and it does: per-bot counts, most read pages, formats (HTML, Markdown, llms.txt, robots.txt) and countries, plus tier-limited fallbacks. Nothing essential is missing for a 2-parameter read tool.

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% and both parameters are documented there, including the days enum and the free-tier 7-day restriction, so the description only reinforces what the schema already says. Baseline 3 applies since the schema does the heavy lifting.

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 ('Shows which AI bots read one site') and enumerates the operators measured (ChatGPT, Claude, Perplexity, Meta, Amazon), which clearly separates it from the sibling get_site_stats general traffic tool. An agent can pick it 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?

Implies the context (AI bot traffic, with change vs previous period) and gives concrete plan-tier conditions: free accounts get 7 days of totals and operator names, PRO unlocks per-bot counts, pages, formats and countries for 7/30/90 days. It never explicitly names an alternative tool or exclusion, so 4 rather than 5.

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.