Skip to main content
Glama
frrazer

roblox-analytics-mcp

by frrazer

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROBLOX_API_KEYNoOpen Cloud API key with the universe-analytics API system and universe.analytics:read scope. Used as a fallback if the key has not been stored via `roblox-analytics-mcp setup`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_metricsA

List the analytics metrics you can query, with each metric's exact (case-sensitive) name, human label, category, supported granularities, data retention in days, and supported breakdown/filter dimensions. Call this first to pick a metric and check which granularity and dimensions it accepts. Filter by category or search by keyword to keep the output small.

query_metricsA

Query a time series for one analytics metric of a Roblox universe (experience): DAU, revenue, retention, playtime, crash rate, funnels, custom events, and more. Returns data points bucketed by granularity, optionally broken down by dimensions (e.g. Platform, Country) and filtered. Each data point has a UTC 'time', a numeric 'value' (or 'stringValues' for text metrics), and may carry a 'status' of Valid, Projected, or NotStatisticallySignificant. Slow queries are polled automatically; if the response has done: false, call get_operation with its 'path'. Requires an API key with the universe.analytics:read scope.

list_dimension_valuesA

Discover the actual values a dimension takes for a metric in a universe over a date range, e.g. which Country codes, Platform names, FunnelName values, CustomEventName values, or Place IDs have data. Use the returned values in query_metrics filters or to understand breakdown results. Returns { values: [{ dimension, values: [{ value }] }] }.

get_operationA

Check on a long-running analytics query. Use this when query_metrics or list_dimension_values returned done: false; pass the 'path' from that response. Returns the operation with 'done' and, once finished, the 'response' payload.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct responsibility: listing available metrics, querying metric time series, discovering dimension values, and polling async operations. There is no overlap in purpose; descriptions clearly separate the two data-retrieval tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (list_metrics, query_metrics, list_dimension_values, get_operation). The naming style is uniform and predictable.

Tool Count5/5

Four tools is an appropriate size for an analytics-focused server: discovery, query, dimension exploration, and async operation handling cover the necessary workflow without bloat. Each tool earns its place.

Completeness5/5

The set covers the full analytics query lifecycle: find a metric, inspect its dimensions, run the query, and retrieve results for long-running operations. There are no obvious dead ends or missing core capabilities.

Maintenance

ActivityMaintained
ResponsivenessNo issues