rybbit-mcp

User Traits

rybbit_get_user_traits

Read-onlyIdempotent

List user trait keys, retrieve distinct trait values, or find users by a specific trait key-value pair.

Instructions

Get user trait keys, values, or find users by trait. mode='keys' lists all trait keys. mode='values' (default when key is provided) returns distinct values for a trait key. mode='users' finds users matching a specific trait key+value pair (case-insensitive).

Input Schema

TableJSON Schema

Name	Required	Description
`key`	No	Trait key (required for 'values' and 'users' modes)
`mode`	No	'keys' to list trait keys, 'values' to get values for a key, 'users' to find users by trait. Default: 'keys' if no key provided, 'values' if key is provided.
`limit`	No	Max results to return
`value`	No	Trait value (required for 'users' mode)
`siteId`	Yes	Site ID (numeric ID or domain identifier)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`keys`	No
`values`	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": {
+    "data": {},
+    "keys": {
+      "items": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "additionalProperties": true,
+            "properties": {
+              "count": {
+                "type": "number"
+              },
+              "key": {
+                "type": "string"
+              },
+              "userCount": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "values": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.5.2Apr 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral detail beyond them: case-insensitive matching in users mode and the implicit mode-default logic. It doesn't mention pagination behavior despite the limit parameter.

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?

Three short sentences, front-loaded with the overall purpose, then one clause per mode. No filler or repetition; every sentence carries distinct information.

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?

An output schema exists, so return-value detail is not required, and annotations cover safety. The description covers all modes and their triggers, leaving only sibling differentiation (vs. rybbit_get_user / rybbit_list_users) unaddressed.

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% and the schema already documents mode semantics, key/value requirements, and limit. The description restates the mode/key relationship, adding only the case-insensitivity note for value matching, so baseline 3 is appropriate.

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?

States a specific verb (Get) and resource (user trait keys/values/users), then enumerates the three operating modes so an agent knows exactly what surface the tool covers. The functional scope is unambiguous even without naming a sibling.

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

Usage Guidelines4/5

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

It explains when each mode applies and even documents the default resolution rule ('values' when key is provided, otherwise 'keys'). What's missing is routing against siblings like rybbit_get_user or rybbit_list_users, which could plausibly overlap.

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

Deploy Server