flayr

Analytics overview

get_analytics

Read-onlyIdempotent

[read-only] Engagement overview for the last 7, 30 or 90 days. Pro plan or higher. (Wraps GET /api/v2/analytics.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`range`	No		30d
`groupBy`	No	A label key (e.g. `cut`, `variant`). Returns the per-label / per-experiment breakdown instead of brand totals: the same body as `GET /api/v2/analytics/experiments?key=<groupBy>` (which also takes `window`, `metric`, `brandId`, `format`, `include`).
`labelKey`	No	FFE-1204: alias of `groupBy`. Use at most one of `groupBy`, `labelKey`, `experimentId` (two → 422).
`experimentId`	No	FFE-1204: one experiment's per-variant results instead of brand totals: the same body as `GET /api/v2/experiments/{id}/results` (incl. % watched per arm; unreported watch data is `null`, never 0).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedInput schema / properties / experimentId

Added value: +{
+  "description": "FFE-1204: one experiment's per-variant results instead of brand totals: the same body as `GET /api/v2/experiments/{id}/results` (incl. % watched per arm; unreported watch data is `null`, never 0).",
+  "type": "string"
+}

addedInput schema / properties / groupBy

Added value: +{
+  "description": "A label key (e.g. `cut`, `variant`). Returns the per-label / per-experiment breakdown instead of brand totals: the same body as `GET /api/v2/analytics/experiments?key=<groupBy>` (which also takes `window`, `metric`, `brandId`, `format`, `include`).",
+  "type": "string"
+}

addedInput schema / properties / labelKey

Added value: +{
+  "description": "FFE-1204: alias of `groupBy`. Use at most one of `groupBy`, `labelKey`, `experimentId` (two → 422).",
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the '[read-only]' prefix adds nothing. The plan-tier requirement and the wrapped GET endpoint are genuinely useful context beyond the annotations, but nothing is said about failures, quotas, or how the two breakdown paths differ in cost.

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?

Two short sentences plus a parenthetical, front-loaded with the scope. The bracketed '[read-only]' is redundant with annotations and is the only wasted token; the rest 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?

No output schema exists, yet the description never indicates what an engagement overview contains beyond 'engagement overview' — no metric list or shape for the three different response bodies it can return. Combined with the omitted mutual-exclusion rule, an agent must read the schema to call it safely.

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?

Schema description coverage is high (75%) and the schema itself documents groupBy, the labelKey alias, the 422 on combining them, and the experimentId equivalence. The description contributes no parameter meaning at all, so baseline 3 is appropriate.

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?

States a specific resource and scope: an engagement overview with a 7/30/90-day window, plus the underlying endpoint it wraps. It distinguishes the default brand-totals mode from per-label/per-experiment breakdowns, though it doesn't directly name which sibling tools (e.g. get_experiment_results) it overlaps with.

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?

Gives a real eligibility gate ('Pro plan or higher') but no explicit when-to-use/when-not-to-use guidance. The routing information that matters (breakdown vs totals; use at most one of groupBy/labelKey/experimentId) lives only in the schema, not the description.

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

All flayr 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?