PostNitro

List Scheduled Posts

postnitro_list_scheduled_posts

Read-onlyIdempotent

List scheduled posts and drafts whose scheduled time falls within a date range. Returns each post with its captions, selected social accounts, and attached design details.

Optionally narrow the results to specific social accounts with socialAccountIds — useful for "what's scheduled on my LinkedIn next week". The filter applies to POSTS, not to the accounts within them: a post targeting both LinkedIn and Instagram is returned when you filter by either, and its accounts array still lists every account it targets.

Input Schema

TableJSON Schema

Name	Required	Description
`toDate`	Yes	End of range (ISO-8601 recommended). Matches scheduledAt <= toDate.
`fromDate`	Yes	Start of range (ISO-8601 recommended). Matches scheduledAt >= fromDate.
`socialAccountIds`	No	Optional social-account IDs (from postnitro_list_social_accounts) to filter by. Returns only posts targeting at least ONE of them. Omit for every post in the range. Unknown IDs are not an error — they simply match nothing, so a filter of only unknown IDs returns an empty list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of posts in the range
`posts`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds important edge-case behavior: filtering applies to posts, not to accounts within posts, and unknown socialAccountIds match nothing rather than causing errors.

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?

The description is concise but complete. It avoids unnecessary detail while covering key behaviors and an example use case, with no redundant or confusing phrasing.

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

Completeness5/5

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

Given the output schema is present and the description covers purpose, filtering behavior, edge cases, and examples, the tool description is fully sufficient for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are fully described in the schema, and the description adds practical details: ISO date recommendations, the 'at least one' account matching rule, the option to omit for all posts, and behavior for unknown IDs.

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 clearly states the tool's purpose: listing scheduled posts and drafts within a date range, with optional account filtering. It distinguishes itself from single-post retrieval by focusing on a date-ranged list operation.

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 clear usage context, including a practical example ('what's scheduled on my LinkedIn next week') and explains filtering semantics. It does not explicitly mention alternative tools, but the guidance is strong enough for correct selection.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources

Need Help?