Skip to main content
Glama

convalytics

by io.github.Dan-Cleary

pageviews_count

Read-onlyIdempotent

Count page views for a specific project in a time window. Page views are the automatic hits captured by the browser script tag (separate from custom events). Use this for web-traffic questions like 'how many pageviews in the last 24 hours'. Default window is the last 7 days. Pass user to scope to one visitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoOptional. Filter to one visitor/user. Accepts userEmail (case-insensitive) or visitorId (exact). For the full per-user snapshot prefer user_activity.
sinceNoStart of window as unix milliseconds. Defaults to 7 days ago.
untilNoEnd of window as unix milliseconds. Defaults to now.
projectYesProject name (case-insensitive, e.g. 'slopbench') or project id from list_projects.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent. Description adds clarity that page views are automatic hits separate from custom events, and mentions default window. No contradictions.

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 concise sentences, front-loaded with purpose. No unnecessary words.

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?

Covers key aspects: what the tool does, default window, user scoping, separation from custom events. Lacks output format description but acceptable for a count tool without output 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 coverage is 100% and well-documented. Description adds minimal value beyond schema (only mentions user scoping and alternative tool). 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?

Clearly states 'Count page views for a specific project in a time window', specifies resource and action, distinguishes from siblings like events_count and user_activity.

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?

Provides an example use case and default window, and mentions alternative user_activity for per-user snapshot. Lacks explicit when-not-to-use but sufficient for common usage.

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

All convalytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

All tools have clearly distinct purposes. Funnel operations (compute, create, delete, get, list, update) are well-separated from event tools (events_count, recent_events) and pageview tools (pageviews_count, top_pages, top_referrers). Composite snapshots (user_activity, weekly_digest) and utility tools (get_usage, list_projects) are unique.

Naming Consistency3/5

Naming pattern is inconsistent: some tools use verb_noun (compute_funnel, create_funnel), others noun_verb (events_count, pageviews_count), and some are adjective_noun (recent_events, top_pages) or noun_noun (user_activity, weekly_digest). While readable, the lack of a consistent convention reduces predictability.

Tool Count4/5

15 tools is at the upper boundary of 'well-scoped' but still appropriate for an analytics platform. Each tool serves a necessary function without unnecessary duplication, though a few more could be justified.

Completeness4/5

The tool set covers core analytics operations: CRUD for funnels, event and pageview counting, top pages/referrers, user and weekly snapshots, and project/usage info. Minor gaps exist (e.g., no session-level detail), but overall it addresses common analytics queries well.

Resources