Narrareach

Add platform to scheduled note

add_platform_to_scheduled_note

Idempotent

Add a platform (or another account on a platform) to a Note that is already scheduled, so it posts there at the same time as the Note's other versions. Use this, not schedule_note, whenever the writer wants an already scheduled Note to also go to X, LinkedIn, Bluesky, Threads, Instagram, Facebook, TikTok or Pinterest: schedule_note would create a separate Note. Pass the id of any scheduled version of the Note (from list_scheduled_items, list_notes or schedule_note) and the platform. Without content the text is taken from the Note's versions (the same platform's version, else the longest that fits) and, if every version is too long, shortened to fit with adjustedPlatforms and warnings returned; content you pass is sent as written and must fit the platform's limit. When the writer has several accounts on the platform, name one with accountId (list_social_accounts; list_instagram_destinations for Instagram; list_linkedin_destinations for LinkedIn, with linkedInOrganizationUrn for a Company Page); without one the call is refused with the accounts to choose from. Ask the writer, never pick. Refused when the Note already goes to that platform or account (or posted there in the last day), when its time has passed or changed, or for Substack. Returns the new version(s) and their scheduled time. Safe to retry: pass a clientRequestId and reuse it only when retrying the same add (same Note and time, platform, account and content); a repeat returns the version already added (replayed: true), and the id reused for any other add is refused. Personal account only.

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": {
      "id": "<id>",
      "platform": "<platform>"
    },
    "name": "add_platform_to_scheduled_note"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Id of any scheduled version of the Note, from list_scheduled_items, list_notes or schedule_note.
`content`	No	Optional text written for this platform, sent as written; it must fit the platform's limit (Bluesky 300, Threads 500, LinkedIn 3000, X 25000). When the Note quotes a Substack Note or post, its link is added as the last line (and counts). Omit to use the Note's own text.
`platform`	Yes	The platform to add.
`accountId`	No	Account to post from: an accountId from list_social_accounts (Threads, Facebook, TikTok, Pinterest, X), list_instagram_destinations (Instagram) or list_linkedin_destinations (LinkedIn). Required when the writer has several accounts on the platform.
`clientRequestId`	No	Optional id for this add (8 to 80 letters, numbers, hyphens or underscores). Reuse it only to retry the same add (same Note and time, platform, account and content); a repeat returns the version already added, and any other add with it is refused.
`linkedInOrganizationUrn`	No	LinkedIn Company Page URN from list_linkedin_destinations, with its accountId.

Output Schema

Name	Required	Description	Default
`added`	Yes
`noteId`	Yes
`draftId`	Yes
`platform`	Yes
`replayed`	Yes
`timezone`	Yes
`versions`	Yes
`warnings`	Yes
`scheduledFor`	Yes
`connectedAccount`	No
`adjustedPlatforms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Far exceeds what the annotations carry. It discloses refusal conditions (already goes to that platform/account or posted in the last day, time passed or changed, Substack), the idempotency contract with clientRequestId and the replayed:true response, and the content fallback logic. These are exactly the behavioral traits an agent cannot derive from readOnlyHint/idempotentHint alone.

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 purpose and the sibling distinction before the operational detail, and each sentence carries real information (refusals, idempotency, content sourcing). It is dense and reads as one long block rather than clearly segmented sections, which taxes scanning, but there is little filler.

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, so return values needn't be spelled out, and the description still notes it returns the new version(s) and scheduled time. Combined with the refusal conditions, account-selection path, and idempotency rules, an agent has everything needed to call this correctly.

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 100%, so the baseline is 3, but the description adds genuine semantics beyond the schema: the omission-fallback rule for content ('the same platform's version, else the longest that fits... shortened to fit with adjustedPlatforms and warnings'), and the account-selection requirement. It clarifies behavior rather than merely restating field descriptions.

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 ('Add a platform (or another account on a platform) to a Note that is already scheduled') plus the downstream effect ('so it posts there at the same time as the Note's other versions'). It explicitly distinguishes itself from the nearest sibling, schedule_note, so an agent can route correctly without opening either schema.

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 an explicit selection rule ('Use this, not schedule_note, whenever...') and explains what schedule_note would do instead (create a separate Note). It also enumerates the platforms in scope and the operating rule 'Ask the writer, never pick', leaving nothing to inference.

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?