Skip to main content
Glama
Sign In

deed.page

by page.deed
OverviewDiscussionsAdmin

Site analytics

site_analytics
Read-onlyIdempotent

Returns owner-only cookieless counts for a slug: views per UTC day, top paths, top referrer hosts, and AI crawler counts by user-agent family. Inputs: slug, optional from and to as YYYY-MM-DD (default the last 7 days; up to 90 days per request on Free and Hobby, 365 on Pro), optional format (json, or csv on Pro), and token. A longer range or csv below Pro returns plan_required with a Pro upgrade link. The accuracy field describes under-counting. No raw IP or full user agent is stored.

Input Schema

NameRequiredDescriptionDefault
toNoLast UTC day, YYYY-MM-DD. Default is today.
fromNoFirst UTC day, YYYY-MM-DD. Default is 6 days before to.
slugYesSlug you own.
tokenNoBearer token returned by your first publish (deed_tok_...). Optional if the MCP client sends Authorization: Bearer.
formatNojson (default) or csv (Pro). csv returns the same counts as text in the csv field, one row per day total, path, referrer host, and crawler family: date,kind,key,views.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "json (default) or csv (Pro). csv returns the same counts as text in the csv field, one row per day total, path, referrer host, and crawler family: date,kind,key,views.",
+  "enum": [
+    "json",
+    "csv"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: auth via token or Authorization header, the plan_required error with an upgrade link for out-of-plan requests, the 'accuracy' field's under-counting caveat, and a privacy statement that no raw IP or full user agent is stored. These are exactly the behavioral facts an agent needs before calling.

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?

Front-loaded with the return payload, then inputs, then error behavior, then the accuracy/privacy caveats — each sentence carries distinct information. It is dense and packs several facts per sentence, which is slightly taxing to scan but wastes no words.

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?

There is no output schema, yet the description names the returned dimensions (daily views, paths, referrer hosts, crawler families), explains the accuracy field, and describes csv row structure. Combined with the plan-limit and auth details, an agent has everything needed to invoke and interpret results correctly.

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; the description earns above that by restating the date defaults (last 7 days), the 90/365-day caps tied to plan, and the csv-is-Pro-only rule, which are constraints the schema does not express. The csv row shape (date,kind,key,views) is also surfaced.

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 ('returns owner-only cookieless counts for a slug') and enumerates exactly which metrics come back: views per UTC day, top paths, top referrer hosts, AI crawler counts by UA family. This clearly separates it from sibling tools like get_site or list_sites, which deal with site metadata rather than analytics.

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?

Gives clear operating context: owner-only access, default range of the last 7 days, and per-plan range caps (90 days Free/Hobby, 365 Pro) with csv gated to Pro. It does not name a sibling alternative or state when-not-to-use it, but the plan/precondition guidance is unusually concrete.

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

All deed.page toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources