Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Event Names

rybbit_get_event_names
Read-onlyIdempotent

Retrieve custom event names and occurrence counts for a Rybbit Analytics site to identify tracked events within specified date ranges and filters.

Instructions

Get all custom event names and their occurrence counts for a site. Useful for discovering what events are being tracked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
startDateNoStart date in ISO format (YYYY-MM-DD)
endDateNoEnd date in ISO format (YYYY-MM-DD)
timeZoneNoIANA timezone (e.g., Europe/Prague). Default: UTC
filtersNoArray of filters. Example: [{parameter:'browser',type:'equals',value:['Chrome']},{parameter:'country',type:'equals',value:['US','DE']}]
pastMinutesStartNoAlternative to dates: minutes ago start (e.g., 60 = last hour)
pastMinutesEndNoAlternative to dates: minutes ago end (default 0 = now)

Implementation Reference

  • The handler and registration logic for the 'rybbit_get_event_names' tool.
    server.registerTool(
      "rybbit_get_event_names",
      {
        title: "Event Names",
        annotations: { readOnlyHint: true, idempotentHint: true, openWorldHint: true, destructiveHint: false },
        description:
          "Get all custom event names and their occurrence counts for a site. Useful for discovering what events are being tracked.",
        inputSchema: {
          ...analyticsInputSchema,
        },
      },
      async (args) => {
        try {
          const params = client.buildAnalyticsParams(args);
          const data = await client.get(`/sites/${args.siteId}/events/names`, params);
          return {
            content: [{ type: "text" as const, text: truncateResponse(data) }],
          };
        } catch (err) {
          const message = err instanceof Error ? err.message : String(err);
          return {
            content: [{ type: "text" as const, text: `Error: ${message}` }],
            isError: true,
          };
        }
      }
    );
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context by specifying the tool returns 'occurrence counts' alongside names and limits scope to 'custom' events (distinguishing from system events). It does not contradict annotations and adds semantic meaning beyond the safety profile.

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 consists of two highly efficient sentences with zero redundancy. The first sentence front-loads the core functionality (getting names and counts), while the second provides the use case (discovery). Every word earns its place.

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?

Given the absence of an output schema, the description appropriately compensates by mentioning 'occurrence counts' to indicate the return structure. Combined with rich annotations covering safety/idempotency and comprehensive input schema, the description is sufficient for a read-only discovery tool, though it could optionally mention pagination or result limits.

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?

With 100% schema description coverage, the schema fully documents all 7 parameters including the complex filters array. The description does not add parameter-specific semantics (e.g., date formats, filter syntax), so the baseline score of 3 is appropriate per the rubric for high schema coverage.

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 specific action ('Get'), resource ('custom event names'), scope ('for a site'), and return data ('occurrence counts'). It distinguishes itself from siblings like rybbit_list_events or rybbit_get_event_properties by focusing specifically on the discovery of event names rather than event instances or detailed analytics.

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?

The description provides contextual guidance stating it is 'Useful for discovering what events are being tracked,' which indicates the exploration/discovery use case. However, it lacks explicit when-not-to-use guidance or references to sibling alternatives (e.g., rybbit_get_event_timeseries for temporal analysis).

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/nks-hub/rybbit-mcp'

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