Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Web Vitals Time Series

rybbit_get_performance_timeseries
Read-onlyIdempotent

Retrieve Core Web Vitals performance metrics as time-series data to analyze trends and monitor website speed over specific periods.

Instructions

Get Core Web Vitals performance metrics as time-series data for trend analysis.

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)
bucketNoTime bucket granularity (default: day). Use 'hour' for last 24h, 'week'/'month' for long ranges

Implementation Reference

  • The handler implementation for the "rybbit_get_performance_timeseries" tool, which fetches time-series performance data from the Rybbit API.
    async (args) => {
      try {
        const { siteId, bucket, ...rest } = args as {
          siteId: string;
          bucket?: string;
          startDate?: string;
          endDate?: string;
          timeZone?: string;
          filters?: Array<{
            parameter: string;
            type: string;
            value: (string | number)[];
          }>;
          pastMinutesStart?: number;
          pastMinutesEnd?: number;
        };
    
        const params = client.buildAnalyticsParams({ ...rest, bucket });
    
        const data = await client.get<PerformanceTimeSeries[]>(
          `/sites/${siteId}/performance/time-series`,
          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,
        };
      }
    }
  • Registration of the "rybbit_get_performance_timeseries" tool within the MCP server.
    server.registerTool(
      "rybbit_get_performance_timeseries",
      {
        title: "Web Vitals Time Series",
        description:
          "Get Core Web Vitals performance metrics as time-series data for trend analysis.",
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true,
          destructiveHint: false,
        },
        inputSchema: {
          ...analyticsInputSchema,
          bucket: bucketSchema,
        },
      },
Behavior3/5

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

Annotations cover safety profile (readOnly, idempotent, non-destructive). Description adds domain specificity (Core Web Vitals) but omits additional behavioral context like pagination, rate limits, or specific metrics returned (LCP, CLS, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence efficiently conveys core purpose with zero waste. However, extreme brevity leaves no room for usage guidance that would help an agent distinguish this from similar tools.

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?

Adequate given the comprehensive input schema (100% coverage), but minimal for a complex 8-parameter analytical tool lacking an output schema. Relies entirely on structured data for completeness.

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 including detailed filter examples. With comprehensive schema documentation, the description appropriately delegates parameter semantics to the structured schema without redundant text.

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 verb 'Get' and resource 'Core Web Vitals performance metrics' with format 'time-series'. Distinguishes from sibling snapshot tools via temporal focus, though does not explicitly name alternatives like 'rybbit_get_performance'.

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 trend analysis') suggesting appropriate use cases, but lacks explicit when-not-to-use guidance or comparison to the singular 'get_performance' snapshot alternative.

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