Skip to main content
Glama

Read what is hitting a site

get_site_traffic
Read-only

Summarizes site traffic over a chosen day window, including bot and crawler requests, errors, busiest endpoints, cache hits, and response times to show crawl costs and block effectiveness.

Instructions

Every request to one of the caller's sites over the last days, summed from the platform's request journal: per day requests, bot requests, 4xx and 5xx; the crawlers by name (Googlebot, Amazonbot, GPTBot, SemrushBot, scripts…) with their request counts; the busiest endpoints (offre/{slug}) and the busiest exact paths, each with its bot share and errors; status codes; cache hits and average duration. Use it to see which robots cost the most, which pages they crawl, and whether a block (robots.txt, a 403 by user agent) took effect. Bots = flagged when recorded, no browser user agent, or one naming a crawler or a tool. Aggregates only: no address, account or full user agent. Days default 7, up to 30.

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": {
      "domainId": "<domainId>"
    },
    "name": "get_site_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days, ending now (default 7).
domainIdYesThe site (from list_domains).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, but the description adds substantial behavioral context: the data is summed from the platform's request journal, results are aggregates only with no address/account/full user agent, and bots are defined by three concrete criteria. It also discloses the default and maximum window, which helps the agent set expectations for the read.

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?

The definition is front-loaded with the core scope and then lists the useful dimensions and caveats. It is dense and somewhat long, but nearly every clause earns its place by describing a returned metric, bot rule, privacy constraint, or usage context.

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?

For a read-only analytics tool with no output schema, the description covers the data source, returned dimensions, bot classification, privacy limitations, and the days window. The remaining details an agent might infer, such as authorization and exact response shape, are not critical for correct invocation.

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 description coverage is 100%, so both parameters are already documented. The description repeats the days default and maximum and implies domainId selects one of the caller's sites, but adds little beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb and resource: reading aggregated request traffic for one of the caller's sites over a day window. It enumerates the exact traffic dimensions returned—daily requests, bots, 4xx/5xx, crawler breakdowns, endpoints, paths, cache hits, and duration—which clearly distinguishes it from visitor or app-analytics siblings.

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?

It gives explicit use cases: seeing which robots cost the most, which pages they crawl, and whether a block took effect. That is clear guidance for when to use it, though it does not name alternatives or say when another traffic/log tool would be more appropriate.

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