Skip to main content
Glama
neverhunt

rybbit-mcp

by neverhunt

Get analytics overview

rybbit_get_overview

Retrieve site analytics metrics including sessions, pageviews, unique users, bounce rate, and average session duration for any date range.

Instructions

Get high-level analytics metrics for a site over a time range: sessions, pageviews, unique users, pages per session, bounce rate, and average session duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesThe Rybbit site ID (numeric ID from your Rybbit dashboard or the rybbit_list_sites tool).
start_dateNoStart date, e.g. 2024-01-01. Use with end_date and time_zone.
end_dateNoEnd date, e.g. 2024-01-31. Use with start_date and time_zone.
time_zoneNoIANA time zone, e.g. America/New_York. Required when using start_date/end_date or start_datetime/end_datetime.
start_datetimeNoExact start datetime, e.g. '2024-01-15 13:00:00' (UTC). Alternative to start_date.
end_datetimeNoExact end datetime, e.g. '2024-01-15 15:00:00' (UTC). Alternative to end_date.
past_minutes_startNoRelative range start in minutes ago, e.g. 60. Use with past_minutes_end instead of dates.
past_minutes_endNoRelative range end in minutes ago, e.g. 0 for 'now'. Use with past_minutes_start.
filtersNoOptional list of filters to narrow the data (AND logic across different filters). Example: [{"parameter":"country","type":"equals","value":["US"]}]
Behavior3/5

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

With no annotations provided, the description carries the full burden. The verb 'Get' and the list of metrics imply a read-only operation, but the description does not explicitly state behavioral traits such as idempotency, side effects, or authorization requirements. It adds some value by indicating the scope (high-level overview) but lacks rich behavioral context.

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?

The description is a single sentence that front-loads the main action and lists the metrics concisely. Every part is relevant, and there is no wasted text. It is appropriately sized for a tool with well-documented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters and no output schema, the description is minimal. It tells what metrics are retrieved but does not explain the output format, constraints, or usage notes for the many parameters. While the schema handles parameter details, the description could be more complete for a complex tool.

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 the baseline is 3. The description only lists the metrics returned and does not add meaning to the parameters beyond what the schema provides. No parameter-specific explanations are added, so the description does not compensate further.

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 clearly states the tool retrieves high-level analytics metrics for a site, listing specific metrics (sessions, pageviews, etc.). It uses a specific verb 'Get' and resource 'analytics overview', making the purpose unambiguous even without explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like rybbit_get_breakdown or rybbit_get_overview_timeseries. There are no prerequisites, exclusions, or context for use, leaving the agent to infer from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/neverhunt/rybbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server