rybbit_list_sitesRetrieve all sites and organizations you have access to in Rybbit Analytics. Use this list to identify available sites for management and analysis.
List all sites and organizations the authenticated user has access to
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, non-destructive, idempotent behavior, so the low bar is met. The description adds access-filtering context ('has access to') but does not mention ordering, pagination, or result shape. This is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler; the action and scope are front-loaded. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only listing with rich annotations, the description is nearly complete. There is no output schema, so a bit more detail about whether the response is a flat list or grouped sites/orgs could help, but it is not essential for selecting and invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters and schema coverage is 100%, so the description need not explain inputs. The baseline for zero-parameter tools is 4; the description accurately implies the call requires no arguments.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb-resource pair ('List all sites and organizations') and adds the access scope ('authenticated user has access to'). This clearly separates it from siblings such as rybbit_list_users and rybbit_get_site_details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The statement makes the intended use obvious: call when you need the full set of sites/organizations visible to the authenticated user. It does not explicitly name alternatives or exclusion conditions, but for a zero-parameter enumeration this is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.