Narrareach

Confirm your Substack connection

verify_substack

Destructive

Compatibility tool for existing connections. New clients can use get_substack_verification_status, start_substack_verification, complete_substack_verification, and cancel_substack_verification for individual operations. Confirm Substack without leaving this conversation or signing in again. Use the exact connectionId from the publishing response or get_user_profile. Check status first. When the user wants to continue, use start to request a code, then ask them for it here. If start returns verified: true, skip code entry. Ask in a normal chat message and wait for the user’s reply; if a prompt closes without an answer, keep waiting in chat without requesting another code. Use complete with the returned id and the code they provide. Never guess a code, repeat submissions automatically, or send the code to another tool. Only the connected account owner can confirm. After completion, poll the existing schedule if its ID is known. Otherwise promptly retry the same saved draft with the original settings; the scheduler checks for an existing matching schedule before creating one. Verification is not proof of scheduling or publishing.

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": {
      "action": "<action>",
      "connectionId": "<connectionId>"
    },
    "name": "verify_substack"
  }
}

Input Schema

Name	Required	Description
`id`	No	Code request id returned by start or status. Required for complete and cancel.
`code`	No	The six-digit code supplied by the user. Required only for complete. Never echo it back.
`action`	Yes
`connectionId`	Yes	The exact Substack connection to confirm.
`scheduledPostId`	No	The exact saved article job from the publishing response. Pass it to resume that same job after verification.

Output Schema

Name	Required	Description	Default
`id`	No
`method`	No
`message`	Yes
`required`	No
`verified`	No
`cancelled`	No
`challenge`	No
`expiresAt`	No
`connection`	No
`nextAction`	No
`instruction`	No
`publication`	Yes
`connectionId`	Yes
`articleRecovery`	No
`resumedArticles`	No
`scheduledPostId`	No
`connectedAccount`	No
`deliveryConfirmed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedOutput schema / properties / articleRecovery / properties / failed
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / articleRecovery / properties / followUp
```
Added value: +{
+  "const": "check_status",
+  "type": "string"
+}
```
- addedOutput schema / properties / articleRecovery / properties / succeeded
```
Added value: +{
+  "type": "integer"
+}
```

Changed3 schema fields changedOct 18, 2026

addedInput schema / properties / scheduledPostId

Added value: +{
+  "description": "The exact saved article job from the publishing response. Pass it to resume that same job after verification.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

changedOutput schema / properties / challenge / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "expiresAt": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "method": {
-        "anyOf": [
-          {
-            "enum": [
-              "email",
-              "totp"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "method",
-      "expiresAt"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "expiresAt": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "method": {
+        "anyOf": [
+          {
+            "enum": [
+              "email",
+              "totp"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "scheduledPostId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "method",
+      "expiresAt"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / scheduledPostId
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 10, 2026
- addedOutput schema / properties / instruction
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / nextAction
```
Added value: +{
+  "const": "wait_for_code",
+  "type": "string"
+}
```
AddedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: only the connected account owner can confirm, codes must never be guessed or sent to another tool, and verification is not proof of scheduling or publishing. It does not explain why the tool has destructiveHint=true, but it does not contradict that annotation either.

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?

The description is front-loaded with purpose and alternatives, then moves through the verification workflow. It is somewhat long and dense for a single paragraph, but most sentences carry operational value and few are 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?

For a five-parameter tool with an output schema, the description covers the main workflow, authorization constraint, code-handling safety, and post-completion scheduling behavior. It is slightly incomplete around cancel semantics and error states, but broadly complete for correct invocation.

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 80%, and the description adds useful meaning by tying connectionId to the publishing response or get_user_profile, explaining the action flow, and clarifying when id, code, and scheduledPostId are used. It does not fully describe when to use cancel, but otherwise goes beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and action: confirming a Substack connection via status/start/complete/cancel operations. It distinguishes itself from the individual sibling tools by naming them and framing this as a compatibility tool for existing connections, though the phrase 'compatibility tool' is slightly vague on its own.

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?

It gives explicit workflow guidance: check status first, use start to request a code, ask the user for the code in chat, skip code entry if start returns verified:true, and use complete with the returned id. It also names the sibling tools for new clients and describes post-completion behavior, leaving little 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?