Replai

Read Agent channel activity

agent_channel_activity_read

Read-onlyIdempotent

Reports each channel's 24-hour inbound count, last inbound time, saved status/reply mode and connection signal for the specified Agent.

Google Email signals describe mailbox state; unknown signals and missing inbound times are null. This reads local records without provider calls; provider_status reports connection state.

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	Agent ID from agents_list or agent_create.

Output Schema

Name	Required	Description	Default
`scope`	No		agent
`agent_id`	Yes	Agent whose channels own this recorded activity.
`channels`	Yes
`workspace_id`	Yes	Dashboard Workspace (tenant) from the current grant.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / agent_id / description
```
Added value: +"Agent ID from agents_list or agent_create."
```

Changed1 schema field changedOct 30, 2026

addedOutput schema / $defs / ChannelActivity / properties / webhook

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "ok",
+        "down",
+        "send_blocked",
+        "recovering",
+        "degraded",
+        "late",
+        "preparing"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Recorded connection signal; for Google Email the mailbox state: send_blocked = mail arrives but replies cannot be sent, late = no successful check for over 15 minutes, recovering = reading missed mail, preparing = first sync.",
+  "title": "Webhook"
+}

First observedOct 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only annotations, the description explains that this reads local records without provider calls, that unknown signals and missing inbound times are null, and that Google Email signals describe mailbox state. These are meaningful behavioral details that help an agent interpret results correctly.

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?

The description is two sentences, front-loads the core output description, and uses the second sentence for important edge-case and locality behavior. Every clause earns its place.

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 and the description still adds useful interpretation context: null handling, provider-call avoidance, and the distinction from provider_status. Combined with the rich read-only annotations, nothing critical is missing.

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?

The schema has 100% description coverage for the single required agent_id parameter, including its source from agents_list or agent_create. The description adds no parameter-level detail beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource, stating that it reports per-channel 24-hour inbound counts, last inbound time, saved status/reply mode, and connection signal for a specified Agent. This is concrete enough to distinguish it from generic channel or analytics siblings.

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 gives clear context for when to use the tool and explicitly points to provider_status for connection state, but it does not mention other potentially competing siblings such as channel_read, line_activity_read, agent_analytics, or agent_kpis_read. The usage context is clear but not exhaustive.

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?