Narrareach

Update voice examples

update_voice_examples

Idempotent

Choose which of the writer's own posts show how they sound, when the writer asks you to: pin posts so they are used first (up to 6), unpin them, exclude posts that are not how they sound, restore excluded posts, or reset to their most recent posts. Example ids come from list_voice_examples. One call is one change the writer can undo.

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

Input Schema

Name	Required	Description
`pin`	No	Example ids to pin.
`reset`	No	true clears every pin and exclusion, back to the writer's most recent posts. Applied before the lists.
`unpin`	No	Pinned example ids to unpin.
`writer`	No	Optional team writer name, handle, or id within the workspace. "me" selects your linked voice. Requires workspace.
`exclude`	No	Example ids the writer says are not how they sound. They are never used as examples.
`restore`	No	Excluded example ids to allow again.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user's personal account.

Output Schema

Name	Required	Description	Default
`undo`	Yes
`pinned`	Yes
`changed`	Yes
`removed`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (not read-only, not destructive, idempotent), and the description adds beyond that: the pin cap ('up to 6'), the fact that exclusions are permanent ('never used as examples'), and that each call is a single undoable change. It doesn't state permission or workspace requirements beyond the schema.

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?

Purpose and the enumeration of actions are front-loaded, and the undo guarantee is a well-placed short follow-up sentence. The first sentence is long and list-heavy, but nothing is wasted.

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?

Covers all seven optional parameters' effects at the operation level and, since an output schema exists, needn't describe return values. Minor gap: no guidance on combining actions in one call beyond the reset-precedence note already in the schema.

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% and the schema already spells out each parameter's meaning (including 'never used as examples' and reset precedence), so the description mostly repeats it. Baseline 3 applies 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?

States a specific verb set (pin/unpin/exclude/restore/reset) on a specific resource (the writer's own example posts) and explains the effect ('show how they sound'). It also routes to list_voice_examples as the id source, distinguishing it from the read-only sibling.

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?

Gives an explicit trigger — 'when the writer asks you to' — and enumerates the five sub-actions with their intent, plus where ids come from. It stops short of naming when NOT to use it versus adjacent tools like add_voice_material or update_voice_stances.

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?