Narrareach

List scheduled posts

list_scheduled_posts

Read-only

List scheduled posts for the authenticated user, ordered by scheduled time ascending.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_scheduled_posts"
  }
}

Input Schema

Name	Required	Description
`to`	No	ISO datetime; only return posts at/before this time.
`from`	No	ISO datetime; only return posts at/after this time.
`limit`	No	Default 25.
`status`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`posts`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedOutput schema / properties / posts / items / properties / outcome

Added value: +{
+  "enum": [
+    "saved_draft"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / posts / items / properties / remoteEditUrl

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

First observedOct 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the ascending-ordering behavior, which is useful context beyond the annotations, but says nothing about pagination or result limits behavior.

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?

A single efficient sentence with the resource and ordering front-loaded and no wasted words. It is arguably too terse given the sibling ambiguity, but structurally clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. The remaining gap is the lack of sibling disambiguation and usage guidance for a list tool with four filter parameters.

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 75%: the to/from/limit parameters are documented in the schema, and status carries an enum. The description adds no parameter-level detail, but with high schema coverage the baseline of 3 is appropriate.

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?

States a specific verb ('List') and resource ('scheduled posts'), plus the scope (authenticated user) and ordering (scheduled time ascending). However, it does not distinguish itself from the very similar sibling 'list_scheduled_items', leaving the agent to infer the difference between a 'post' and an 'item'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, despite the presence of near-neighbors like list_scheduled_items and list_social_posts. There are also no exclusions or prerequisites stated, so selection relies entirely on the agent's 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?