Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Event Properties

rybbit_get_event_properties
Read-onlyIdempotent

Analyze custom event data by retrieving distinct property keys and values with occurrence counts for specified time periods and filters.

Instructions

Get property breakdowns for a specific custom event. Returns the distinct property keys and values with counts.

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)
eventNameYesEvent name to get properties for

Implementation Reference

  • The handler and registration for 'rybbit_get_event_properties' are defined together in registerEventsTools using server.registerTool. The tool queries the /events/properties endpoint of the Rybbit API.
    server.registerTool(
      "rybbit_get_event_properties",
      {
        title: "Event Properties",
        annotations: { readOnlyHint: true, idempotentHint: true, openWorldHint: true, destructiveHint: false },
        description:
          "Get property breakdowns for a specific custom event. Returns the distinct property keys and values with counts.",
        inputSchema: {
          ...analyticsInputSchema,
          eventName: z.string().describe("Event name to get properties for"),
        },
      },
      async (args) => {
        try {
          const params = client.buildAnalyticsParams(args);
          params.event_name = args.eventName;
          const data = await client.get(`/sites/${args.siteId}/events/properties`, 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 cover safety (readOnly/idempotent). Description adds return value structure ('distinct property keys and values with counts') which is necessary given no output schema. Omits behavioral details like error handling for non-existent events, pagination, or rate limits.

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?

Two sentences with zero waste. Front-loaded with action verb 'Get'. Second sentence efficiently describes return value. No redundant or filler text.

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?

Sufficient for a read-only tool with full schema coverage: explains return format (compensating for missing output schema) and core purpose. Gaps remain regarding parameter interaction guidance (e.g., pastMinutes vs date range exclusivity) and filter usage patterns given the complexity of the filters array.

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 has 100% description coverage with all 8 parameters documented. Description reinforces the 'eventName' parameter via 'specific custom event' but adds no additional semantic detail for complex parameters like 'filters' or date alternatives. Baseline 3 appropriate given schema completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action 'Get property breakdowns' and target 'specific custom event'. The second sentence clarifies return content ('distinct property keys and values with counts'). Does not explicitly differentiate from siblings like rybbit_get_event_names or rybbit_get_event_timeseries.

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?

Provides implied usage context ('for a specific custom event'), suggesting use when analyzing a particular event's attributes. Lacks explicit when-to-use guidance versus alternatives (e.g., when to use rybbit_get_event_timeseries instead) or prerequisites.

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