Skip to main content
Glama
neverhunt

rybbit-mcp

by neverhunt

Get a dimensional breakdown (top pages, referrers, countries, browsers, etc.)

rybbit_get_breakdown

Break down website analytics by dimension like page, country, or browser to see traffic, pageviews, and bounce rate per value.

Instructions

Get analytics broken down by a single dimension, ranked by traffic. Use this for questions like 'what are the top pages', 'where is traffic coming from', 'what countries/browsers/devices do visitors use', 'what are the top UTM campaigns', etc. Set parameter to the dimension to break down by, e.g.: pathname, page_title, hostname, referrer, channel, entry_page, exit_page, country, region, city, browser, browser_version, operating_system, device_type, language, utm_source, utm_medium, utm_campaign, utm_term, utm_content, event_name. Results include visit count, percentage of total, pageviews, and bounce rate per value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesThe Rybbit site ID (numeric ID from your Rybbit dashboard or the rybbit_list_sites tool).
parameterYesDimension to break down by, e.g. pathname, referrer, country, browser, device_type, utm_source, channel.
limitNoMax number of rows to return (default applies if omitted).
pageNoPage number for pagination (1-indexed).
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"]}]
Behavior4/5

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

No annotations are provided, so the description covers the behavioral aspects: it returns results with visit count, percentage, pageviews, bounce rate. It lists valid dimension values and filter options. No mention of side effects, but tool is read-only by nature.

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 sentences, front-loaded with purpose and examples. Every sentence adds necessary context without verbosity.

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?

Despite 12 parameters and no output schema, the description explains the output fields, covers all parameter categories, and provides usage examples. It is sufficiently complete for an AI agent to invoke 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% with descriptions for each parameter. The description adds value by listing example dimension values and explaining the filter structure in detail, which goes beyond the schema.

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 it 'Get analytics broken down by a single dimension, ranked by traffic' and provides concrete example questions. It distinguishes itself from sibling tools like overview or session tools by focusing on breakdowns.

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?

The description includes example usage scenarios like 'what are the top pages', making it clear when to use. It does not explicitly exclude alternative tools, but the use cases are well-defined.

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