Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Session Locations

rybbit_get_session_locations
Read-onlyIdempotent

Retrieve geographic session data with coordinates for map visualization and location analysis. Specify site, date range, and filters to get latitude, longitude, city, and country information.

Instructions

Get geographic session location data with coordinates. Returns latitude, longitude, city, country, and session count for map visualization and geographic analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
startDateNoStart date in ISO format (YYYY-MM-DD)
endDateNoEnd date in ISO format (YYYY-MM-DD)
timeZoneNoIANA timezone (e.g., Europe/Prague). Default: UTC
filtersNoArray of filters. Example: [{parameter:'browser',type:'equals',value:['Chrome']},{parameter:'country',type:'equals',value:['US','DE']}]
pastMinutesStartNoAlternative to dates: minutes ago start (e.g., 60 = last hour)
pastMinutesEndNoAlternative to dates: minutes ago end (default 0 = now)
pageNoPage number, 1-indexed (default: 1)
limitNoResults per page (default: 20-50 depending on endpoint, max 200)

Implementation Reference

  • The handler function for 'rybbit_get_session_locations' tool. It constructs parameters and calls the Rybbit client to fetch session location data.
    async (args) => {
      try {
        const params = client.buildAnalyticsParams(args);
    
        const data = await client.get(
          `/sites/${args.siteId}/session-locations`,
          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,
        };
      }
    }
  • Registration of the 'rybbit_get_session_locations' tool with the MCP server, including its schema, title, description, and annotations.
    server.registerTool(
      "rybbit_get_session_locations",
      {
        title: "Session Locations",
        description:
          "Get geographic session location data with coordinates. Returns latitude, longitude, city, country, and session count for map visualization and geographic analysis.",
        inputSchema: {
          ...analyticsInputSchema,
          ...paginationSchema,
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
      },
Behavior4/5

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

Annotations establish read-only, idempotent, non-destructive behavior. The description adds value by detailing the specific return fields (latitude, longitude, city, country, session count) and intended use cases, effectively compensating for the lack of output schema.

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?

Two sentences with zero waste. First sentence states purpose and data type, second specifies return values and use case. Efficiently front-loaded with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully compensates by enumerating the returned data fields. Combined with comprehensive input schema (100% coverage) and complete annotations, the description provides sufficient context for invocation.

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?

Input schema has 100% description coverage, so baseline 3 is appropriate. The description focuses on return values rather than input parameter semantics, which is acceptable given the comprehensive 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?

Clear specific verb 'Get' and resource 'geographic session location data with coordinates'. Explicitly distinguishes from siblings like rybbit_get_session or rybbit_get_user by focusing on geographic/geolocation data.

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?

Provides clear usage context specifying the tool is for 'map visualization and geographic analysis'. While it doesn't explicitly name alternative tools, the context makes it clear when to use (geographic analysis) versus other analytics tools.

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