Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

List Sites

rybbit_list_sites
Read-onlyIdempotent

Retrieve all accessible sites and organizations for authenticated users to manage analytics data and monitor website statistics.

Instructions

List all sites and organizations the authenticated user has access to

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'rybbit_list_sites', which fetches all organizations and their associated sites using the provided RybbitClient.
    server.registerTool(
      "rybbit_list_sites",
      {
        title: "List Sites",
        description:
          "List all sites and organizations the authenticated user has access to",
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
      },
      async () => {
        try {
          const data = await client.get<Organization[]>("/organizations");
    
          return {
            content: [
              {
                type: "text" as const,
                text: truncateResponse(data),
              },
            ],
          };
        } catch (err) {
          const message = err instanceof Error ? err.message : String(err);
          return {
            content: [{ type: "text" as const, text: `Error: ${message}` }],
            isError: true,
          };
        }
      }
    );
Behavior4/5

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

The annotations cover safety (readOnlyHint, destructiveHint) and idempotency. The description adds valuable context about the authorization model ('authenticated user has access to') and clarifies that the tool returns both sites AND organizations, which is not obvious from the name alone.

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?

The description is a single, efficient sentence of 11 words. Every word earns its place: the verb ('List'), the scope ('all'), the resources ('sites and organizations'), and the access control boundary ('authenticated user has access to').

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?

Given the tool's simplicity (zero parameters) and the presence of comprehensive annotations, the description is sufficiently complete. It compensates for the missing output schema by mentioning both 'sites and organizations' in the return. A perfect score would require explicit mention of the return format or pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema contains zero parameters, establishing a baseline score of 4. The description appropriately does not invent parameters, and the phrase 'authenticated user has access to' confirms no additional filtering parameters are accepted.

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 clearly states the action ('List') and resources ('sites and organizations') being accessed. It implicitly distinguishes from sibling tools like rybbit_get_site_id (singular) and rybbit_create_site (mutation) by emphasizing 'all sites,' though it does not explicitly name alternatives.

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 description mentions 'authenticated user has access to,' providing implicit context about authorization boundaries. However, it lacks explicit guidance on when to use this versus rybbit_get_site_id or other retrieval tools, and does not mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nks-hub/rybbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server