PostNitro

Get Scheduled Post

postnitro_get_scheduled_post

Read-onlyIdempotent

Fetch a single scheduled post by ID, with its captions, selected social accounts, platform settings, attached design details, and publishing status.

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": {
      "scheduledPostId": "<scheduledPostId>"
    },
    "name": "postnitro_get_scheduled_post"
  }
}

Input Schema

Name	Required	Description	Default
`scheduledPostId`	Yes	The scheduled-post ID (get from postnitro_list_scheduled_posts)

Output Schema

Name	Required	Description	Default
`post`	Yes	A scheduled post or draft

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedOutput schema / properties / post / properties / pinterestPostSettings
```
Added value: +{
+  "$ref": "#/properties/post/properties/instagramPostSettings"
+}
```
Changed1 schema field changedSep 29, 2026
- addedOutput schema / properties / post / properties / facebookPostSettings
```
Added value: +{
+  "$ref": "#/properties/post/properties/instagramPostSettings"
+}
```
First observedSep 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds what content the response contains, but no additional behavioral context such as error behavior for unknown IDs or any access restrictions. With annotations carrying the safety burden, this is adequate but not rich.

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?

A single front-loaded sentence that names the action, the lookup key, and the payload contents with no filler. Every clause earns its place.

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?

With rich annotations, a fully documented parameter, and an output schema covering return values, the description needs only to state the resource and scope, which it does. Minor gap: no note about behavior when the ID does not exist or refers to a deleted post.

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?

Only one parameter exists and schema description coverage is 100%, with the schema itself explaining the ID and its source. The description adds nothing beyond 'by ID', so the baseline 3 applies.

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 ('Fetch a single scheduled post by ID') and enumerates the returned facets (captions, social accounts, platform settings, design details, publishing status). An agent can distinguish it from postnitro_list_scheduled_posts, postnitro_update_scheduled_post, and postnitro_get_brand without opening any schema.

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: it is clearly the single-item counterpart to postnitro_list_scheduled_posts, and the schema's parameter description tells the agent where to obtain the ID ('get from postnitro_list_scheduled_posts'). There is no explicit statement of when to prefer this over the list tool or what happens on an invalid/missing ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PostNitro 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?