Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Site Overview

rybbit_get_overview
Read-onlyIdempotent

Retrieve aggregated website analytics metrics including sessions, pageviews, unique users, bounce rate, and session duration for specified date ranges with customizable filters.

Instructions

Get aggregated overview metrics for a site: sessions, pageviews, unique users, pages per session, bounce rate, and average session duration. Supports date range and filters.

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

  • Registration of the 'rybbit_get_overview' tool.
    server.registerTool(
      "rybbit_get_overview",
      {
        title: "Site Overview",
        description:
          "Get aggregated overview metrics for a site: sessions, pageviews, unique users, pages per session, bounce rate, and average session duration. Supports date range and filters.",
        inputSchema: {
          ...analyticsInputSchema,
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
      },
  • The handler function for 'rybbit_get_overview' which fetches overview metrics from the Rybbit API.
      async (args) => {
        try {
          const params = client.buildAnalyticsParams({
            startDate: args.startDate,
            endDate: args.endDate,
            timeZone: args.timeZone,
            filters: args.filters,
            pastMinutesStart: args.pastMinutesStart,
            pastMinutesEnd: args.pastMinutesEnd,
          });
    
          const data = await client.get<OverviewMetrics>(
            `/sites/${args.siteId}/overview`,
            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,
          };
        }
      }
    );
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive traits. The description adds valuable behavioral context by listing the specific metrics returned in the overview, which is crucial information given the lack of an output schema. No contradictions with annotations exist.

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, efficient sentence that front-loads the action and resource. Every clause earns its place: the colon-separated list specifies return values, and the final phrase indicates filtering capabilities without verbosity.

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 lack of an output schema, the description appropriately compensates by enumerating the six key metrics returned. It adequately covers the tool's purpose for a 7-parameter analytics endpoint, though it could explicitly mention the alternative time-range parameters (pastMinutes) as mutually exclusive options to date ranges.

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 baseline is established. The description mentions 'date range and filters' but does not add semantic meaning, syntax examples, or clarify the relationship between date-based and pastMinutes-based parameters beyond what the schema already provides.

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 aggregated overview metrics'), target resource ('site'), and enumerates the exact metrics returned (sessions, pageviews, unique users, etc.). The term 'aggregated' effectively distinguishes this from the sibling 'rybbit_get_overview_timeseries' tool.

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?

While the description implies use for high-level site analytics by listing overview metrics, it lacks explicit guidance on when to choose this over 'rybbit_get_overview_timeseries' (trends vs. totals) or 'rybbit_get_metric' (single metric). No prerequisites or exclusions are mentioned.

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