rybbit-mcp

Update Site Config

rybbit_update_site_config

Idempotent

Update an existing Rybbit site's configuration: identity, tracking features, exclusions, session replay, and public embedding.

Instructions

Update configuration for an existing Rybbit site. Change site identity (name, domain, type), toggle tracking features (IP, session replay, errors, button clicks, etc.), manage exclusions (IPs, countries, paths, hostnames, user agents), and public embedding.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Display name for the site
`tags`	No	Tags for grouping/filtering sites (max 20, each up to 50 chars)
`type`	No	Site type: 'web' or 'mobile'. 'app' is a legacy alias mapped to 'mobile'. Switching to mobile forces sessionReplay and webVitals off.
`domain`	No	Domain (web sites) or package name (mobile sites). Normalized server-side.
`public`	No	Make site stats publicly accessible
`siteId`	Yes	Site ID (numeric ID or domain identifier)
`trackIp`	No	Track visitor IP addresses
`blockBots`	No	Block known bots from tracking
`trackCopy`	No	Track text copy events
`webVitals`	No	Track Core Web Vitals metrics
`excludedIPs`	No	IP addresses or CIDR ranges to exclude from tracking (max 100)
`saltUserIds`	No	Salt user IDs for privacy
`trackErrors`	No	Track JavaScript errors
`embedEnabled`	No	Allow embedding public stats (e.g. via iframe)
`excludedPaths`	No	URL path patterns to exclude from tracking (max 100)
`sessionReplay`	No	Enable session replay recording
`trackOutbound`	No	Track outbound link clicks
`trackUrlParams`	No	Track URL parameters
`excludedCountries`	No	ISO 3166-1 alpha-2 country codes to exclude from tracking (max 250)
`excludedHostnames`	No	Hostnames to exclude from tracking (max 100)
`trackButtonClicks`	No	Track button click events
`excludedUserAgents`	No	User-agent substrings/patterns to exclude from tracking (max 100)
`trackSpaNavigation`	No	Track SPA navigation events
`trackInitialPageView`	No	Track initial page view automatically
`trackFormInteractions`	No	Track form interaction events

Output Schema

TableJSON Schema

Name	Required	Description	Default
`config`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.8.1Sep 28, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain (web sites) or package name (app sites). Normalized server-side."New value: +"Domain (web sites) or package name (mobile sites). Normalized server-side."

addedInput schema / properties / embedEnabled

Added value: +{
+  "description": "Allow embedding public stats (e.g. via iframe)",
+  "type": "boolean"
+}

addedInput schema / properties / excludedHostnames

Added value: +{
+  "description": "Hostnames to exclude from tracking (max 100)",
+  "items": {
+    "maxLength": 253,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / excludedPaths

Added value: +{
+  "description": "URL path patterns to exclude from tracking (max 100)",
+  "items": {
+    "maxLength": 2048,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / excludedUserAgents

Added value: +{
+  "description": "User-agent substrings/patterns to exclude from tracking (max 100)",
+  "items": {
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Site type: 'web' or 'mobile'. 'app' is a legacy alias mapped to 'mobile'. Switching to mobile forces sessionReplay and webVitals off.",
+  "enum": [
+    "web",
+    "mobile",
+    "app"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "config": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedv0.4.3Apr 30, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Domain (web sites) or package name (app sites). Normalized server-side.",
+  "maxLength": 253,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / excludedCountries

Added value: +{
+  "description": "ISO 3166-1 alpha-2 country codes to exclude from tracking (max 250)",
+  "items": {
+    "maxLength": 2,
+    "minLength": 2,
+    "pattern": "^[A-Z]{2}$",
+    "type": "string"
+  },
+  "maxItems": 250,
+  "type": "array"
+}

addedInput schema / properties / excludedIPs

Added value: +{
+  "description": "IP addresses or CIDR ranges to exclude from tracking (max 100)",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Display name for the site",
+  "maxLength": 255,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Tags for grouping/filtering sites (max 20, each up to 50 chars)",
+  "items": {
+    "maxLength": 50,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

First observedv0.5.2Apr 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), and the description's only added behavioral fact is that the target site must be existing. It does not disclose partial-update semantics (whether omitted fields are preserved or reset), required permissions, or the side effects noted in the schema (e.g. switching to mobile forcing sessionReplay/webVitals off).

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?

A single front-loaded sentence opens with the core action and then lists the configurable domains in parallel verb groups, so an agent can scan it quickly. It is slightly list-heavy but contains no filler or repetition.

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?

For a 25-parameter mutation tool with an output schema (so return values need no explanation) and annotations covering the safety profile, the description is adequate but leaves one important gap: whether the update is a partial patch or a full replace, which matters a great deal when most fields are optional. Auth/permission requirements are also unmentioned.

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 description coverage is 100%, so every one of the 25 parameters is already documented in the schema, which sets the baseline at 3. The description groups fields into identity, tracking toggles, exclusions, and embedding, which is a mild navigational aid, but it adds no syntax, format, or interaction detail beyond what the schema already provides.

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?

The description states a specific verb and resource ('Update configuration for an existing Rybbit site') and enumerates the configuration domains touched, so an agent can immediately tell this is a mutation tool for an existing site rather than rybbit_create_site. It does not explicitly contrast itself with the sibling rybbit_get_config (read path) or rybbit_create_site, so it falls short of full sibling differentiation.

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 phrase 'for an existing Rybbit site' implies the precondition (the site must already exist) but the description never states when to reach for this tool over siblings like rybbit_create_site or rybbit_get_config, nor does it say when not to use it. Usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server