rybbit-mcp

Update Goal

rybbit_update_goal

Idempotent

Update an existing goal's name, type, or configuration for a Rybbit Analytics site, including path patterns, event names, and property filters.

Instructions

Update an existing goal's name, type, or configuration.

Input Schema

Name	Required	Description
`name`	No
`config`	Yes	Goal configuration. Use pathPattern for path goals or eventName for event goals.
`goalId`	Yes	Numeric goal ID to update
`siteId`	Yes	Site ID (numeric ID or domain identifier)
`goalType`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`message`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.1Sep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "type": [
+        "string",
+        "number"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Addedv0.5.1Apr 30, 2026
RemovedApr 30, 2026
Addedv0.4.3Apr 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare that this is a non-read-only, idempotent, and non-destructive write operation. The description adds no behavioral context beyond what the annotations provide, such as update semantics (full replace vs. merge), authorization requirements, or side effects.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a minimal update tool, though its extreme brevity contributes to gaps in guidance and behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters including a required nested config object, 4 required fields), the description is too sparse. While annotations cover safety and an output schema exists, the description fails to explain update semantics, how config interacts with goalType, or whether omitted fields are preserved.

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 60%, and the description only restates the mutable fields ('name, type, or configuration') without adding format details, dependencies, or examples. The schema itself handles most parameter semantics, so this is baseline adequate.

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 an existing goal') and names the mutable fields (name, type, configuration). It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like rybbit_create_goal or rybbit_delete_goal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'existing goal' implies use for modification, but there is no explicit guidance on when to use this versus rybbit_create_goal, nor any prerequisites or exclusions. The description gives minimal context for tool selection.

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

Deploy Server