Narrareach

Cancel a Substack code request

cancel_substack_verification

DestructiveIdempotent

Cancel the selected code request for the connected account owner. Does not cancel article schedules, delete drafts, or disconnect Substack. Use only when the user wants to cancel this verification request.

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": {
      "connectionId": "<connectionId>",
      "id": "<id>"
    },
    "name": "cancel_substack_verification"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The code request id returned for this same connection.
`connectionId`	Yes	The exact Substack connection from the publishing response or get_user_profile.
`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 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuine beyond-schema context by enumerating what is NOT affected (schedules, drafts, Substack connection), bounding the blast radius of a destructive operation; it does not state whether cancellation is reversible or what happens if the request already expired.

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?

Two sentences, no filler, with the core action stated first and the negative scope immediately after. The 'Use only when' clause is the last and most restrictive detail, which is the right ordering.

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?

Output schema and annotations carry the return shape and safety/idempotency semantics, and all parameters are documented, so the description only needed to pin down scope — which it does. Minor gap: no mention that a live/pending verification request must exist, or how the agent recovers if the id is stale.

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%, so all three parameters (id, connectionId, scheduledPostId) are already fully documented, including the resume-after-verification purpose of scheduledPostId. The description contributes only 'the selected code request' and 'connected account owner', adding no syntax, format, or resolution guidance beyond the schema.

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 ('Cancel') and resource ('code request') scoped to 'the connected account owner', and then explicitly carves out adjacent operations (article schedules, drafts, Substack connection) so the agent can separate it from cancel_scheduled_item, cancel_scheduled_post, and verify_substack.

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?

Provides a clear positive trigger ('Use only when the user wants to cancel this verification request') plus three explicit exclusions, which is strong guidance. It stops short of naming the directly competing siblings (complete_substack_verification, start_substack_verification, get_substack_verification_status), so the agent must infer the verification-workflow alternatives.

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?