Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

List Goals

rybbit_list_goals
Read-onlyIdempotent

Retrieve all goals for a website with current conversion metrics and configuration details to analyze performance.

Instructions

List all goals for a site with their current conversion metrics and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
startDateNoStart date (YYYY-MM-DD)
endDateNoEnd date (YYYY-MM-DD)
timeZoneNoIANA timezone (default UTC)
filtersNoFilters to apply
pastMinutesStartNoMinutes ago start
pastMinutesEndNoMinutes ago end

Implementation Reference

  • Registration of the 'rybbit_list_goals' tool.
    server.registerTool(
      "rybbit_list_goals",
      {
        title: "List Goals",
        description:
          "List all goals for a site with their current conversion metrics and configuration.",
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true,
          destructiveHint: false,
        },
        inputSchema: {
          siteId: siteIdSchema,
          startDate: z
            .string()
            .optional()
            .describe("Start date (YYYY-MM-DD)"),
          endDate: z
            .string()
            .optional()
            .describe("End date (YYYY-MM-DD)"),
          timeZone: z
            .string()
            .optional()
            .describe("IANA timezone (default UTC)"),
          filters: z
            .array(filterSchema)
            .optional()
            .describe("Filters to apply"),
          pastMinutesStart: z
            .number()
            .optional()
            .describe("Minutes ago start"),
          pastMinutesEnd: z
            .number()
            .optional()
            .describe("Minutes ago end"),
        },
      },
  • Handler implementation for 'rybbit_list_goals'.
    async (args) => {
      try {
        const { siteId, ...rest } = args as {
          siteId: string;
          startDate?: string;
          endDate?: string;
          timeZone?: string;
          filters?: Array<{
            parameter: string;
            type: string;
            value: (string | number)[];
          }>;
          pastMinutesStart?: number;
          pastMinutesEnd?: number;
        };
    
        const params = client.buildAnalyticsParams(rest);
    
        const data = await client.get<Goal[]>(
          `/sites/${siteId}/goals`,
          params
        );
        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,
        };
      }
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds value by disclosing that the tool returns 'conversion metrics and configuration' beyond just goal IDs. However, it does not mention pagination behavior, rate limits, or whether the 'current' metrics respect the date filters (which are available parameters).

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, efficient sentence of 11 words. Main verb 'List' appears first, followed by resource and qualifiers. No redundant or filler text. Every word earns its place.

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 7 parameters including complex date ranges and filters, the description is minimally adequate. It compensates somewhat for the missing output schema by mentioning 'conversion metrics and configuration'. However, it fails to clarify the temporal scope (supports historical ranges via startDate/endDate) and the word 'current' may misleadingly suggest real-time-only data.

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, the baseline is 3. The description does not add semantic meaning beyond the schema (e.g., explaining the relationship between startDate/endDate and pastMinutes, or providing examples of filter construction). It mentions 'site' which maps to siteId, but this is minimal additional context.

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?

Clearly states the action (List), resource (goals), and return content (conversion metrics and configuration). Distinguishes from sibling tools like rybbit_list_sites or rybbit_get_goal_sessions by specifying 'goals' and 'configuration'. However, it does not explicitly differentiate from rybbit_get_goal_sessions which retrieves session-level data rather than goal definitions.

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?

Provides no guidance on when to use this versus alternatives like rybbit_get_goal_sessions or rybbit_list_funnels. Does not mention prerequisites (e.g., needing a valid siteId) or when to prefer date ranges versus pastMinutes parameters.

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