Narrareach

Get note

get_note

Read-only

Get a single scheduled or posted note by id, including full content, recent stored metric snapshots (with Substack follows and subscriptions), platformMetrics, the connected account it names (socialAccountId) and why it is waiting if held (failureCode).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ScheduledAutoPost id.
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user’s personal account.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`draft`	Yes
`error`	Yes
`quote`	Yes
`status`	Yes
`content`	Yes
`context`	Yes
`itemUrl`	Yes
`postUrl`	Yes
`platform`	Yes
`postedAt`	Yes
`timezone`	Yes
`createdAt`	Yes
`updatedAt`	Yes
`retryCount`	Yes
`contentHash`	Yes
`contentJson`	Yes	A JSON value stored by Narrareach.
`contentMeta`	Yes	A JSON value stored by Narrareach.
`contentType`	Yes
`scheduledFor`	Yes
`externalPostId`	Yes
`platformMetrics`	Yes
`connectedAccount`	No
`distributionKind`	Yes
`performanceSnapshots`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedOutput schema / properties / quote

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "enum": [
+            "note",
+            "post"
+          ],
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "kind"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "context",
-  "id",
-  "itemUrl",
-  "platform",
-  "status",
-  "contentType",
-  "content",
-  "contentJson",
-  "contentMeta",
-  "distributionKind",
-  "contentHash",
-  "scheduledFor",
-  "timezone",
-  "postedAt",
-  "postUrl",
-  "externalPostId",
-  "error",
-  "retryCount",
-  "createdAt",
-  "updatedAt",
-  "draft",
-  "performanceSnapshots",
-  "platformMetrics"
-]New value: +[
+  "context",
+  "id",
+  "itemUrl",
+  "platform",
+  "status",
+  "contentType",
+  "content",
+  "contentJson",
+  "contentMeta",
+  "distributionKind",
+  "quote",
+  "contentHash",
+  "scheduledFor",
+  "timezone",
+  "postedAt",
+  "postUrl",
+  "externalPostId",
+  "error",
+  "retryCount",
+  "createdAt",
+  "updatedAt",
+  "draft",
+  "performanceSnapshots",
+  "platformMetrics"
+]

Changed6 schema fields changedOct 16, 2026

addedOutput schema / properties / performanceSnapshots / items / properties / follows

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

addedOutput schema / properties / performanceSnapshots / items / properties / freeSubscriptions

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

addedOutput schema / properties / performanceSnapshots / items / properties / paidSubscriptions

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

changedOutput schema / properties / performanceSnapshots / items / required

Previous value: -[
-  "likes",
-  "comments",
-  "shares",
-  "impressions",
-  "clicks",
-  "recordedAt"
-]New value: +[
+  "likes",
+  "comments",
+  "shares",
+  "impressions",
+  "clicks",
+  "follows",
+  "freeSubscriptions",
+  "paidSubscriptions",
+  "recordedAt"
+]

addedOutput schema / properties / platformMetrics

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "clicks": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "comments": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "follows": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "impressions": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "likes": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "observedAt": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "reach": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "reposts": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "saves": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sends": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "shares": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "views": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "likes",
+        "comments",
+        "shares",
+        "saves",
+        "sends",
+        "clicks",
+        "views",
+        "reach",
+        "impressions",
+        "follows",
+        "reposts",
+        "observedAt"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "context",
-  "id",
-  "itemUrl",
-  "platform",
-  "status",
-  "contentType",
-  "content",
-  "contentJson",
-  "contentMeta",
-  "distributionKind",
-  "contentHash",
-  "scheduledFor",
-  "timezone",
-  "postedAt",
-  "postUrl",
-  "externalPostId",
-  "error",
-  "retryCount",
-  "createdAt",
-  "updatedAt",
-  "draft",
-  "performanceSnapshots"
-]New value: +[
+  "context",
+  "id",
+  "itemUrl",
+  "platform",
+  "status",
+  "contentType",
+  "content",
+  "contentJson",
+  "contentMeta",
+  "distributionKind",
+  "contentHash",
+  "scheduledFor",
+  "timezone",
+  "postedAt",
+  "postUrl",
+  "externalPostId",
+  "error",
+  "retryCount",
+  "createdAt",
+  "updatedAt",
+  "draft",
+  "performanceSnapshots",
+  "platformMetrics"
+]

Changed4 schema fields changedOct 16, 2026
- addedOutput schema / properties / performanceSnapshots / items / properties / clicks / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / performanceSnapshots / items / properties / clicks / type
```
Removed value: -"integer"
```
- addedOutput schema / properties / performanceSnapshots / items / properties / impressions / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / performanceSnapshots / items / properties / impressions / type
```
Removed value: -"integer"
```
First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare this is read-only, non-destructive, and closed-world. The description adds some useful context by noting stored metric snapshots and failureCode for held notes, but it does not cover auth requirements, rate limits, or freshness beyond 'stored'; since an output schema exists, much of the return-field listing is redundant.

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?

It is a single front-loaded sentence with no filler, starting with the core action. The long trailing enumeration of return fields is somewhat redundant given the output schema, but the description remains compact and structured.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, the description is sufficient to understand what it fetches and key returned/held-note details. It is only missing explicit sibling routing guidance, which keeps it from being fully complete.

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 coverage is 100%, so the schema already documents both id and workspace. The description only says 'by id' and adds no meaning about the workspace parameter or id format beyond what the schema provides, which matches the baseline for high schema coverage.

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 description states a specific verb and resource: 'Get a single scheduled or posted note by id.' The singular, id-based scope distinguishes it from list-oriented siblings such as list_notes and list_scheduled_posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'by id' and 'single ... note'; the description does not explicitly say when to use this versus list_notes, get_draft, or get_scheduled_item_readiness. It gives enough context to infer a direct lookup when an id is known, but no explicit routing guidance.

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?