Narrareach

Cancel scheduled post

cancel_scheduled_post

Destructive

Cancel a scheduled article. Before its time it cancels the same way as cancel_scheduled_item, including removing the schedule from LinkedIn, Substack and Medium. Once its time has passed, or after it failed, only the Narrareach schedule is cancelled and nothing is removed from the platform, because it may already be live. Already-published posts cannot be cancelled. Returns the new status.

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>"
    },
    "name": "cancel_scheduled_post"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	ScheduledPost id.

Output Schema

Name	Required	Description	Default
`id`	Yes
`status`	Yes
`message`	No
`remoteEditUrl`	No
`alreadyCancelled`	No
`connectedAccount`	No
`cancellationQueued`	No
`remoteDraftRetained`	No
`linkedInResyncRequired`	No
`providerRemovalSkipped`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 1, 2026

addedOutput schema / properties / cancellationQueued
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / linkedInResyncRequired
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / providerRemovalSkipped

Added value: +{
+  "items": {
+    "enum": [
+      "SUBSTACK",
+      "MEDIUM"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / remoteDraftRetained
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / remoteEditUrl

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing exactly what is destroyed in each case: external platform removal before the scheduled time, versus internal-only schedule removal afterwards, on the grounds the post may already be live. This is precisely the operational nuance the agent needs and is fully consistent with destructiveHint=true and idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly four tight sentences, front-loaded with the core action and then ordered by the decision-relevant case (before time, after time/failure, already published), ending with the return value. No sentence is redundant.

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 destructive single-parameter tool with an output schema present, the description covers the mutation semantics, the platform-level side effects, the timing-dependent branches, and the hard exclusion. It even notes the return shape despite an output schema existing, so nothing material is missing.

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?

There is a single required parameter with 100% schema description coverage ("ScheduledPost id."), so the schema already carries full burden. The description adds no format, sourcing, or resolution detail for the id beyond what the schema states, 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?

The first sentence gives a specific verb and resource ("Cancel a scheduled article"), and the opening of the second sentence explicitly positions it relative to the sibling cancel_scheduled_item, which handles the analogous operation for other item types. An agent can identify this as the article-specific cancellation tool without opening the schema.

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?

It provides clear conditional context for when the behavior differs: before the scheduled time it removes the post from LinkedIn, Substack and Medium; after the time has passed or a failure, only the Narrareach schedule is cancelled. It also states an explicit exclusion (already-published posts cannot be cancelled). It stops short of a routing instruction telling the agent to prefer cancel_scheduled_item for non-article items, leaving that inference to the reader.

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?