Skip to main content
Glama

Pagetool

Visits to a site

site_stats
Read-onlyIdempotent

Page views and unique visitors per day for a published site, plus its top pages and the websites that sent visitors. Counted on the server with no cookies; search bots, previews and Pagetool's own checks are not counted. days defaults to 30 (max 90). Free.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, including today (UTC). Default 30, max 90.
site_keyNoThe site whose visits to read. Must be yours (or granted to the operator token).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: counting is server-side with no cookies, bots/previews/internal checks are excluded, the 90-day ceiling, and that the call is free (no quota/billing impact). It does not mention data freshness or latency for today's figures, which is the main remaining gap.

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 short sentences, front-loaded with what is returned, then methodology, then the limit. Every sentence carries information, though the days default/max clause duplicates what the schema already says and could be trimmed.

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 no output schema, the description does the work of describing the return content: per-day views and unique visitors, top pages, and referring websites. Combined with annotations and full schema coverage this is nearly complete; only freshness of the current day's data and the window semantics (UTC, including today) are left to the schema.

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% and both parameters already document their meaning, including the days default of 30 and max of 90 and the ownership requirement for site_key. The description restates the days default/max without adding new semantics. Baseline 3 applies since the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource: reads page views, unique visitors per day, top pages and referrers for a published site. An agent can tell this apart from site-management siblings like list_sites or live_check without opening the schema. It stops short of naming any alternative tool, but no close sibling performs the same analytics role.

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?

Usage context is implied rather than stated: the tool is for a 'published site', so an unpublished site is implicitly out of scope. There is no explicit when-to-use vs when-not framing, and no guidance on how to obtain the required site_key or what happens if the site is not published.

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