rybbit-mcp

Create Goal

rybbit_create_goal

Create a new conversion goal for a site, either as a URL path match or custom event trigger, to track user actions.

Instructions

Create a new conversion goal for a site. Goal can be path-based (URL match) or event-based (custom event triggered).

Input Schema

Name	Required	Description
`name`	No	Optional display name for the goal
`config`	Yes	Goal configuration. Use pathPattern for path goals or eventName for event goals.
`siteId`	Yes	Site ID (numeric ID or domain identifier)
`goalType`	Yes	'path' = URL pattern, 'event' = custom event

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

B3.3/5.0

Behavior3/5

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

Annotations declare this is a non-readOnly, non-idempotent, non-destructive, non-openWorld write operation, which is accurate. The description adds the meaningful distinction between path and event goals, but says nothing about auth requirements, whether goals can be duplicated, or what happens on conflict. It doesn't contradict annotations.

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 short sentences, front-loaded with the core action and resource, then the key branching distinction. No waste.

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?

Given a nested config object, enum goalType, 100% schema coverage, and an output schema, the description covers the essential branching. However, for a create/mutation tool it omits when to use it vs siblings and any prerequisite or conflict behavior. Adequate but with clear gaps.

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 coverage is 100%, so all four parameters (including the nested config object with its own descriptions and enum) are fully documented in the schema. The description mentions path vs event which maps to goalType, but adds no syntax or format details beyond what the schema already provides. Baseline 3.

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 a specific verb (Create) and resource (conversion goal for a site), and distinguishes the two goal variants (path-based vs event-based). It doesn't explicitly differentiate from sibling tools like create_funnel or update_goal, but the resource is specific enough.

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?

No guidance on when to use this versus update_goal, create_funnel, or list_goals. The description mentions two goal types but doesn't explain when each is appropriate beyond a one-line parenthetical. No prerequisites (e.g., site must exist) are stated.

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

Deploy Server