Narrareach

Check scheduled item readiness

get_scheduled_item_readiness

Read-onlyIdempotent

Inspect one scheduled Note or Article using stored Narrareach evidence without contacting a provider. Returns revision, draftId, destination, timing, cover, subscribe controls, paywall, email delivery, stored remote receipt, issues, and next action. Article draft content is local and is not a provider-verified copy; queued Note content is stored on the scheduled Note. pendingScheduleChange reports a Substack time change waiting on the writer’s code: scheduledFor stays the current time until the code is entered, which applies it without sending the change again.

Input Schema

Name	Required	Description	Default
`id`	Yes
`kind`	No

Output Schema

Name	Required	Description	Default
`id`	Yes
`kind`	Yes
`title`	Yes
`checks`	Yes
`issues`	Yes
`status`	Yes
`draftId`	Yes
`itemUrl`	Yes
`revision`	Yes
`timezone`	Yes
`platforms`	Yes
`readiness`	Yes
`nextAction`	Yes
`deliveryNote`	Yes
`destinations`	Yes
`scheduledFor`	Yes
`schemaVersion`	Yes
`contentEditing`	Yes
`accountCanChange`	Yes
`connectedAccount`	No
`articleBodySource`	Yes
`pendingScheduleChange`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

addedOutput schema / properties / pendingScheduleChange

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "connectionId": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "requestedAt": {
+          "anyOf": [
+            {
+              "format": "date-time",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "requestedScheduledFor": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "requestedTimezone": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "verificationRequired": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requestedScheduledFor",
+        "requestedTimezone",
+        "requestedAt",
+        "verificationRequired",
+        "connectionId"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "id",
-  "itemUrl",
-  "kind",
-  "revision",
-  "title",
-  "status",
-  "scheduledFor",
-  "timezone",
-  "platforms",
-  "destinations",
-  "checks",
-  "readiness",
-  "nextAction",
-  "issues",
-  "deliveryNote",
-  "accountCanChange",
-  "draftId",
-  "articleBodySource",
-  "contentEditing"
-]New value: +[
+  "schemaVersion",
+  "id",
+  "itemUrl",
+  "kind",
+  "revision",
+  "title",
+  "status",
+  "scheduledFor",
+  "timezone",
+  "platforms",
+  "destinations",
+  "checks",
+  "readiness",
+  "nextAction",
+  "issues",
+  "deliveryNote",
+  "accountCanChange",
+  "pendingScheduleChange",
+  "draftId",
+  "articleBodySource",
+  "contentEditing"
+]

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / contentEditing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mediaChangesSupported": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "supported": {
+      "type": "boolean"
+    },
+    "tool": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "supported",
+    "reason",
+    "message",
+    "tool",
+    "mediaChangesSupported"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "id",
-  "itemUrl",
-  "kind",
-  "revision",
-  "title",
-  "status",
-  "scheduledFor",
-  "timezone",
-  "platforms",
-  "destinations",
-  "checks",
-  "readiness",
-  "nextAction",
-  "issues",
-  "deliveryNote",
-  "accountCanChange",
-  "draftId",
-  "articleBodySource"
-]New value: +[
+  "schemaVersion",
+  "id",
+  "itemUrl",
+  "kind",
+  "revision",
+  "title",
+  "status",
+  "scheduledFor",
+  "timezone",
+  "platforms",
+  "destinations",
+  "checks",
+  "readiness",
+  "nextAction",
+  "issues",
+  "deliveryNote",
+  "accountCanChange",
+  "draftId",
+  "articleBodySource",
+  "contentEditing"
+]

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / checks / properties / substackAudience

Added value: +{
+  "description": "Who can read past the opening on Substack: freewall (free and paid subscribers), paywall (paid subscribers below the wall), paid_subscribers (whole post), or everyone.",
+  "enum": [
+    "freewall",
+    "paywall",
+    "paid_subscribers",
+    "everyone",
+    "not_applicable"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / checks / required

Previous value: -[
-  "coverImage",
-  "subscribeButtons",
-  "paywall",
-  "emailDelivery",
-  "remoteReceipt"
-]New value: +[
+  "coverImage",
+  "subscribeButtons",
+  "paywall",
+  "substackAudience",
+  "emailDelivery",
+  "remoteReceipt"
+]

Changed4 schema fields changedOct 12, 2026

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

addedOutput schema / properties / destinations / items / properties / accountId

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

changedOutput schema / properties / destinations / items / required

Previous value: -[
-  "platform",
-  "kind",
-  "label"
-]New value: +[
+  "platform",
+  "kind",
+  "label",
+  "accountId"
+]

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "id",
-  "itemUrl",
-  "kind",
-  "revision",
-  "title",
-  "status",
-  "scheduledFor",
-  "timezone",
-  "platforms",
-  "destinations",
-  "checks",
-  "readiness",
-  "nextAction",
-  "issues",
-  "deliveryNote",
-  "draftId",
-  "articleBodySource"
-]New value: +[
+  "schemaVersion",
+  "id",
+  "itemUrl",
+  "kind",
+  "revision",
+  "title",
+  "status",
+  "scheduledFor",
+  "timezone",
+  "platforms",
+  "destinations",
+  "checks",
+  "readiness",
+  "nextAction",
+  "issues",
+  "deliveryNote",
+  "accountCanChange",
+  "draftId",
+  "articleBodySource"
+]

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / deliveryNote

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

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "id",
-  "itemUrl",
-  "kind",
-  "revision",
-  "title",
-  "status",
-  "scheduledFor",
-  "timezone",
-  "platforms",
-  "destinations",
-  "checks",
-  "readiness",
-  "nextAction",
-  "issues",
-  "draftId",
-  "articleBodySource"
-]New value: +[
+  "schemaVersion",
+  "id",
+  "itemUrl",
+  "kind",
+  "revision",
+  "title",
+  "status",
+  "scheduledFor",
+  "timezone",
+  "platforms",
+  "destinations",
+  "checks",
+  "readiness",
+  "nextAction",
+  "issues",
+  "deliveryNote",
+  "draftId",
+  "articleBodySource"
+]

First observedOct 1, 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 (readOnly, idempotent, non-destructive, closed-world), yet the description adds real value: no provider contact, local vs provider-verified provenance for article vs note content, and the pendingScheduleChange state machine where scheduledFor stays stale until a code is entered and applied without resending. The enumerated return-field list is largely redundant with the output 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 is front-loaded and the caveats follow in a logical order. The long run-on enumeration of return fields ('revision, draftId, destination, timing, cover, subscribe controls...') is verbose given an output schema exists, but the remaining sentences earn their place.

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 read-only inspection tool with a full output schema and rich annotations, the description covers the non-obvious parts an agent needs: evidence source, content provenance limits, and pendingScheduleChange behavior. Only the meaning of 'id' is missing, which the schema should carry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does not. It never says what 'id' identifies (scheduled item id vs draft id) or that 'kind' selects between note and article; 'one scheduled Note or Article' only vaguely gestures at the enum.

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 with explicit scope: 'Inspect one scheduled Note or Article.' The readiness framing plus 'using stored Narrareach evidence' separates it from get_note, get_draft, and list_scheduled_items without the agent needing to open a 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?

'Using stored Narrareach evidence without contacting a provider' gives a clear selection cue against the provider-facing siblings (verify_substack, complete_substack_verification), but no sibling is named explicitly and there are no stated exclusions or preconditions for calling it.

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?