Narrareach

List voice examples

list_voice_examples

Read-onlyIdempotent

List the writer's own posts, newest first, that can be pinned as examples of how they sound, with the example ids update_voice_examples takes. Search by text or date and page with nextCursor. Also returns which posts are pinned and which are excluded. Posts outside the writer's main languages, that read like a reply to someone else, or that began as a Narrareach draft (startedFromDraft) are marked: they are never chosen automatically but can be pinned. A note sent to several platforms is listed once, as its Substack copy when there is one.

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_voice_examples"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional latest post date: YYYY-MM-DD (UTC, through the end of the day) or an ISO date-time with offset.
`from`	No	Optional earliest post date: YYYY-MM-DD (UTC) or an ISO date-time with offset.
`query`	No	Optional text to search the posts for.
`cursor`	No	Optional nextCursor from the previous page.
`writer`	No	Optional team writer name, handle, or id within the workspace. "me" selects your linked voice. Requires workspace.
`pageSize`	No	Optional posts per page, 1-20. Defaults to 10.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user's personal account.

Output Schema

Name	Required	Description	Default
`whose`	Yes
`pinned`	Yes
`removed`	Yes
`examples`	Yes
`pinLimit`	Yes
`nextCursor`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedOutput schema / properties / examples / items / properties / startedFromDraft
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / examples / items / required

Previous value: -[
-  "exampleId",
-  "text",
-  "platform",
-  "postedAt",
-  "pinned",
-  "inMainLanguage",
-  "readsAsReply"
-]New value: +[
+  "exampleId",
+  "text",
+  "platform",
+  "postedAt",
+  "pinned",
+  "inMainLanguage",
+  "readsAsReply",
+  "startedFromDraft"
+]

AddedOct 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds real value beyond them: newest-first ordering, the marking/exclusion rule, the dedup rule that a multi-platform note appears once as its Substack copy, and cursor paging via nextCursor.

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?

Four sentences, front-loaded with purpose and workflow linkage before the exclusion and dedup details. Slightly dense in the third sentence, but every clause carries usable information about how results are shaped.

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?

With an output schema present, return values need no explanation, yet the description still conveys ordering, filtering, paging, pin/exclusion status, and dedup behavior. Combined with annotations covering the safety profile, an agent has everything needed to call and interpret this correctly.

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 the schema already documents every parameter including the date formats, pageSize bounds, and cursor semantics. The description only adds a high-level gloss ('search by text or date and page with nextCursor') without syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('List the writer's own posts') plus the exact downstream consumer ('the example ids update_voice_examples takes'), which separates it from siblings like list_voice_changes or list_inspiration_posts. The ordering ('newest first') and filterability are stated up front.

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?

Clearly ties the tool to the update_voice_examples workflow and explains that marked posts are 'never chosen automatically but can be pinned,' which tells the agent how to treat results. It lacks an explicit 'do not use this for X' exclusion against sibling list tools, so it falls short of a 5.

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?