Skip to main content
Glama

Get site traffic statistics

get_site_stats
Read-onlyIdempotent

Returns traffic statistics for one site: page views and daily unique visitors per day, totals and change vs the previous period. On Hostilo PRO also top countries, traffic sources (google, chatgpt, facebook, direct…), devices, browsers, operating systems and top pages, for 7, 30, 90 or 365 days. Free accounts get the last 7 days without breakdowns. Bots are excluded; no cookies or IP addresses are used.

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

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. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.app\" (from list_sites)."New value: +"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.page\" (from list_sites)."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavioral detail: bot exclusion, the no-cookies/no-IP privacy stance, and tier-based truncation of results and breakdowns. What is missing is anything about data freshness or latency, so it falls just short of exhaustive.

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 sentences, front-loaded with the core return value before the tier-specific breakdown list, and no filler. The enumeration of breakdown dimensions is long but each item is load-bearing information for deciding whether to call it.

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?

There is no output schema, so the description has to describe the return values itself, and it does — metrics, per-day granularity, totals, and period-over-period change, plus the optional dimension breakdowns. Only details like response shape or units are left implicit, which is minor for a two-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the breakdowns and periods are tier-dependent, so a free account passing days=365 or expecting country/source data will get less than it asked for. That tier-conditioned interpretation of both parameters is genuine added value.

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?

"Returns traffic statistics for one site" pairs a specific verb with a specific resource and then enumerates the exact metrics (page views, daily unique visitors, totals, change vs previous period) plus the optional breakdowns. That enumeration lets an agent distinguish it from siblings such as get_ai_traffic or get_site without reading any schema.

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?

The description conveys useful applicability context (which periods are available, that free accounts are limited to the last 7 days, that breakdowns require PRO), which implies when the tool is useful. However, it never states when to prefer this over the sibling get_ai_traffic or any other alternative, and offers no explicit exclusions.

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.