Narrareach

List article stats and clicked links

list_article_stats

Read-onlyIdempotent

Read saved stats for the writer’s published articles, newest first: views, opens, open and click rates, reactions, comments, shares, new subscribers, and the links readers clicked (Substack only) with each link’s clicks and share of openers. Pass publicationId for one article. Reads what Narrareach last saved (statsAsOf); it does not fetch from the platforms.

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": "list_article_stats"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Articles per page. Defaults to 20.
`cursor`	No	nextCursor from the previous page.
`platform`	No	Only articles published to this platform.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user’s personal account.
`publicationId`	No	One published article, from a previous list_article_stats result.

Output Schema

Name	Required	Description	Default
`articles`	Yes
`nextCursor`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 12, 2026

TDQS

A4/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, so safety needs no explanation. The description contributes genuinely new behavioral context: results are ordered newest first, clicked-link data is Substack-only, and the figures are a saved snapshot (statsAsOf) rather than live platform data — a staleness caveat an agent could not get from annotations.

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 sentences, both load-bearing, with the core purpose and the returned field list front-loaded before the important caveat about not fetching from platforms. The field enumeration is long but justified because it defines scope; no filler sentences.

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?

Five optional parameters, an output schema, and rich annotations mean the description only needs to add scope and the caching caveat — which it does. The staleness note and the Substack-only restriction on link data are the two things an agent could not otherwise know, and both are present.

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 100%, so limit, cursor, platform, workspace, and publicationId are already fully documented in the schema. The description only restates publicationId's single-article behavior and adds ordering ('newest first'), which is not attached to any parameter, so it adds little meaning beyond the structured fields.

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 opens with a specific verb and resource ('Read saved stats for the writer's published articles') and then enumerates exactly what comes back: views, opens, open and click rates, reactions, comments, shares, subscribers, and clicked links with clicks and share of openers. The parenthetical '(Substack only)' and the closing note that it reads what Narrareach last saved rather than fetching from platforms sharply distinguish it from a live-refresh sibling like refresh_medium_stats.

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?

Usage is implied by 'reads what Narrareach last saved ... it does not fetch from the platforms', which tells an agent not to reach for this when fresh platform data is needed, and 'Pass publicationId for one article' covers the single-article case. However, no sibling tool is named and there is no explicit routing to get_stats_snapshot, get_stats_insights, or the refresh tools, leaving the agent to infer when this cached view is preferable.

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?