Skip to main content
Glama
neverhunt

rybbit-mcp

by neverhunt

List sessions

rybbit_list_sessions

Retrieve paginated visitor sessions with detailed analytics: location, browser, device, referrer, entry/exit pages, pageview and event counts, duration, and UTM parameters. Filter by date range, user, or custom conditions.

Instructions

Get a paginated list of visitor sessions with details: location, browser/OS/device, referrer, entry/exit pages, pageview and event counts, duration, and UTM params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesThe Rybbit site ID (numeric ID from your Rybbit dashboard or the rybbit_list_sites tool).
pageNoPage number, 1-indexed.
limitNoNumber of sessions per page.
user_idNoFilter to sessions for a specific Rybbit user_id.
identified_onlyNoSet to restrict to sessions with an identified user (per Rybbit's identify() API).
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"]}]
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions pagination and returned fields but omits important aspects like rate limits, authentication requirements, or any side effects. For a read-only listing tool, more context is expected.

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?

Single, well-structured sentence that front-loads the main action and includes key details without extraneous information.

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

Completeness2/5

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

Despite 13 parameters and no output schema, description only outlines output fields. It lacks guidance on filtering, ordering, or default pagination sizes, leaving significant gaps 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 coverage is 100%, so description adds no extra meaning beyond parameter names. The description focuses on output, not input parameters, meeting baseline but not exceeding.

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?

Description clearly states 'Get a paginated list of visitor sessions' with specific details like location, browser, etc. It differentiates from sibling tools (e.g., get_session for single session, get_breakdown for different aggregation).

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?

Description implies use for listing sessions but does not explicitly guide when to choose this over siblings. No 'when to use' or 'when not to use' information is provided.

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