Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

User Detail

rybbit_get_user
Read-onlyIdempotent

Retrieve comprehensive user analytics including traits, session history, and activity data from Rybbit Analytics to understand user behavior and engagement patterns.

Instructions

Get detailed information about a specific user including their traits, session history, and activity summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
userIdYesUser ID (identified_user_id or internal user ID)

Implementation Reference

  • The handler implementation for the `rybbit_get_user` tool, which fetches details for a specific user.
      async (args) => {
        try {
          const data = await client.get(`/sites/${args.siteId}/users/${args.userId}`);
          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,
          };
        }
      }
    );
  • The registration block for the `rybbit_get_user` tool.
    server.registerTool(
      "rybbit_get_user",
      {
        title: "User Detail",
        annotations: { readOnlyHint: true, idempotentHint: true, openWorldHint: true, destructiveHint: false },
        description:
          "Get detailed information about a specific user including their traits, session history, and activity summary.",
        inputSchema: {
          siteId: siteIdSchema,
          userId: z.string().describe("User ID (identified_user_id or internal user ID)"),
        },
      },
Behavior4/5

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

Annotations declare readOnly/idempotent/safe properties, so the description doesn't need to cover those. It adds valuable behavioral context by specifying exactly what data categories are returned (traits, session history, activity summary), which annotations and schema don't provide. No contradictions with 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?

Single sentence, front-loaded with the action verb, followed by resource specificity, then detailed scope. Zero waste—every phrase serves to clarify what the tool returns versus siblings.

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?

Despite lacking an output schema, the description compensates by enumerating the three primary data components returned (traits, history, activity). For a 2-parameter read operation with strong annotations, this provides sufficient context for invocation decisions.

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?

With 100% schema description coverage (siteId and userId both fully documented), the description appropriately focuses on behavior rather than repeating parameter definitions. Baseline 3 is correct as the description adds no parameter syntax but none is needed given complete schema documentation.

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?

The description uses specific verb 'Get' with clear resource 'user' and details the scope via 'detailed information' and specific data categories (traits, session history, activity summary). It distinguishes from sibling tools like rybbit_get_user_traits (which presumably returns only traits) and rybbit_list_users (which returns a list rather than detailed individual data).

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 implies this is a comprehensive user lookup by listing multiple data categories (traits, session history, activity), suggesting use when broad user context is needed. However, it lacks explicit guidance on when to prefer alternatives like rybbit_get_user_traits (for trait-only queries) or rybbit_list_users (for discovery).

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