Replai

Read Agent analytics

agent_analytics

Read-onlyIdempotent

Reads one Agent's traffic summary, daily trends and channel breakdown for at most 365 days.

Covers conversation, message and user counts and response time. Resolution and handoff figures are not part of it; agent_kpis_read carries them. channel_type filters summary only; trends and channel breakdown cover all channels, matching the existing product services. No Workspace-wide aggregate is implied.

Input Schema

Name	Required	Description
`agent_id`	Yes	Agent ID from agents_list or agent_create.
`end_date`	Yes	End date (YYYY-MM-DD); the ordered range contains at most 365 days.
`start_date`	Yes	Start date (YYYY-MM-DD) for this Agent traffic report.
`channel_type`	No	Channel-type filter for summary only; trends and channel breakdown include all types.

Output Schema

Name	Required	Description	Default
`scope`	Yes
`trends`	Yes
`summary`	Yes
`agent_id`	Yes
`workspace_id`	Yes
`channel_breakdown`	Yes
`trends_channel_filter`	Yes
`summary_channel_filter`	Yes
`breakdown_channel_filter`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- removedOutput schema / $defs / AgentAnalyticsSummary / properties / anonymous_percentage
```
Removed value: -{
-  "default": 0,
-  "title": "Anonymous Percentage",
-  "type": "number"
-}
```
- removedOutput schema / $defs / AgentAnalyticsSummary / properties / identified_percentage
```
Removed value: -{
-  "default": 0,
-  "title": "Identified Percentage",
-  "type": "number"
-}
```

Changed4 schema fields changedOct 30, 2026

addedInput schema / properties / agent_id / description

Added value: +"Agent ID from agents_list or agent_create."

addedInput schema / properties / channel_type / description

Added value: +"Channel-type filter for summary only; trends and channel breakdown include all types."

addedInput schema / properties / end_date / description

Added value: +"End date (YYYY-MM-DD); the ordered range contains at most 365 days."

addedInput schema / properties / start_date / description

Added value: +"Start date (YYYY-MM-DD) for this Agent traffic report."

First observedOct 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely non-obvious traits: the 365-day maximum range, the fact that channel_type narrows only the summary while trends and channel breakdown stay global, and that no workspace aggregate is produced. It does not mention pagination, empty-range handling, or error conditions.

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?

The scope and the sibling exclusion are front-loaded in the first two lines, and the tool's limits follow in order of importance. The phrase 'matching the existing product services' is internal rationale that adds little for an agent, and the hard line breaks make it slightly choppier than necessary.

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

Completeness4/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 not be explained, and all four parameters are fully described in the schema. Combined with the annotations, the description covers everything needed to select and call the tool correctly; only edge-case behavior such as invalid ranges or large-result handling is absent.

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 coverage is 100%, so the schema already documents every parameter including the agent_id lookup source, date formats and the 365-day range constraint. The description restates the channel_type scoping but adds no syntax or format detail beyond the schema's own text. This is the expected baseline when the schema does the heavy lifting.

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?

The description states a specific verb and resource ('Reads one Agent's traffic summary, daily trends and channel breakdown') with an explicit scope cap of 365 days. It immediately distinguishes itself from agent_kpis_read by naming the figures it does not cover, so an agent can tell the two reporting tools apart without opening either schema.

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?

It explicitly routes resolution and handoff metrics to agent_kpis_read and rules out workspace-wide aggregation, giving clear when-to-use and when-not-to-use boundaries. It stops short of naming the sibling that does cover workspace-level totals (e.g. workspace_primary_agent_dashboard), leaving that routing step to inference.

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

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