AI Agent Analytics

List analytics products

list_products

Read-onlyIdempotent

List the active product in the bearer token's organization. Use this for setup and identity checks; use get_daily_pulse for the customer's current precomputed 24-hour snapshot. The current Founder plan supports one active product. Requires products:read or products:create; invalid or expired authority fails closed, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`schema`	Yes	Response schema identifier.
`products`	Yes	Active products visible to this authorization.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 19, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"This tool takes no parameters."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "products": {
+      "description": "Active products visible to this authorization.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "created_at": {
+            "description": "UTC ISO-8601 product creation timestamp.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Stable product/property ID to pass as product_id to product-scoped tools.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Customer-visible product name.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Current product state.",
+            "type": "string"
+          },
+          "time_zone": {
+            "description": "IANA time zone used for product-local daily metrics.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "status",
+          "time_zone",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schema": {
+      "description": "Response schema identifier.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema",
+    "products"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes well beyond them with auth scopes (products:read or products:create), fail-closed behavior on invalid/expired authority, a concrete rate limit (300 calls/60s per caller), and the 429 + Retry-After failure mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose then the alternative then operational constraints. Dense but every clause (plan limit, scopes, rate limit) carries operational weight; only the packed final sentence slightly reduces readability.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description adds auth requirements, throttling behavior, plan limits, and sibling routing, leaving nothing an agent needs in order to call this correctly.

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 tool takes zero parameters and the schema explicitly documents that ('This tool takes no parameters'), so there is nothing for the description to clarify. Baseline 4 applies; no additional parameter meaning is needed or missing.

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?

States a specific verb and resource with explicit scope: 'List the active product in the bearer token's organization.' It also names the sibling tool get_daily_pulse and what that tool covers instead, so an agent can route without opening a schema. The singular/plural mismatch with the tool name is explained by the stated plan constraint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('setup and identity checks') and a named alternative with its distinguishing condition ('get_daily_pulse for the customer's current precomputed 24-hour snapshot'). It also states the plan-level constraint that only one active product is supported.

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

All AI Agent Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?