Narrareach

Get platform analytics

get_platform_analytics

Read-onlyIdempotent

Read analytics for a connected platform. If a connection is required, returns action_required with connection guidance; do not repeatedly retry until the writer connects. Returns account-level summary data where available, otherwise stored Narrareach note performance and connection readiness. Reads stored data and never refreshes connections (X adds live account numbers when its token is current); for Medium, call refresh_medium_stats first if no stats are stored. Note metrics: impressions and clicks are null when the platform does not report them, not 0. For SUBSTACK, benchmark is the latest saved notes benchmark (see its analysedAt); refresh it with refresh_substack_benchmark. For Substack notes, clicks is the total_clicks count Substack reports for the note; Substack does not document which clicks it includes, and impressions are not available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "get_platform_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	Yes
`recentLimit`	No	How many recent posts/notes to include. Default 10.

Output Schema

Name	Required	Description
`code`	No
`note`	No
`handle`	No
`reason`	No
`source`	No
`status`	No
`totals`	No
`message`	No
`profile`	No
`summary`	No
`nextStep`	No
`platform`	Yes
`username`	No
`verified`	No
`benchmark`	No
`connected`	Yes
`fetchedAt`	No
`followers`	No
`following`	No
`readiness`	No
`growthData`	No
`tweetCount`	No
`cachedStats`	No	A JSON value stored by Narrareach.
`displayName`	No
`publication`	No
`recentNotes`	No
`recentPosts`	No
`statsCachedAt`	No
`engagementData`	No
`profilePicture`	No
`connectedAccount`	No
`verifiedFollowers`	No
`analyticsAvailable`	No
`needsExtensionSync`	No
`postAnalyticsAvailable`	No
`profileAnalyticsAvailable`	No
`officialAnalyticsAvailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedOutput schema / properties / code

Added value: +{
+  "enum": [
+    "ANALYTICS_CONNECTION_REQUIRED"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "action": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "action",
+    "url"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "action_required"
+  ],
+  "type": "string"
+}

Changed10 schema fields changedOct 16, 2026
- addedOutput schema / properties / followers / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / followers / type
```
Removed value: -"integer"
```
- addedOutput schema / properties / following / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / following / type
```
Removed value: -"integer"
```
- addedOutput schema / properties / tweetCount / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tweetCount / type
```
Removed value: -"integer"
```
- addedOutput schema / properties / verified / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / verified / type
```
Removed value: -"boolean"
```
- addedOutput schema / properties / verifiedFollowers / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / verifiedFollowers / type
```
Removed value: -"integer"
```
First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower, and the description still adds substantial behavior: an action_required response with connection guidance, a no-refresh staleness contract, X's token-dependent live numbers, and null-vs-zero semantics for impressions/clicks. These are exactly the operational traits an agent cannot infer from structured fields.

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?

Front-loads the purpose and the connection-failure behavior, which are the highest-value facts, and every sentence carries real information. The density of platform caveats crammed into one paragraph makes it harder to scan than a bulleted layout would.

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?

For a read tool over ten heterogeneous platforms with an output schema already defining return shape, the description covers the remaining unknowns: connection prerequisites, staleness, per-platform refresh paths, and metric null semantics. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is only 50%, and the description never mentions recentLimit (whose schema description already covers it). It does compensate well for the undocumented platform enum by attaching platform-specific meaning to X, Medium, and SUBSTACK values, which the enum list alone would not convey.

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?

Opens with a specific verb+resource ('Read analytics for a connected platform') and explicitly separates itself from the refresh siblings (refresh_medium_stats, refresh_substack_benchmark) by stating it 'never refreshes connections'. It does not, however, distinguish itself from plausibly-overlapping read siblings such as get_stats_snapshot, get_stats_insights, or get_audience_overview.

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 concrete when-to-use routing: call refresh_medium_stats first for Medium if no stats are stored, and use refresh_substack_benchmark to update the Substack benchmark. It also states a when-not-to-do behavior ('do not repeatedly retry until the writer connects'), which is exactly the kind of exclusion an agent needs.

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

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