list_scheduled_posts
List upcoming scheduled posts.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Postlia
by com.postlia
TDQS
B3.3/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is read-only, requires authentication, or returns full data. It simply restates the tool's name without adding extra context.
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 a single sentence, front-loaded, and contains no unnecessary words. It is concise and to the point.
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?
The tool is simple with no parameters, but the description could be more complete by explaining what 'upcoming' means (e.g., based on publish time) and whether results are ordered. Without an output schema, the agent lacks full context on what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the input schema covers everything vacuously. The description does not add parameter info, but with 0 parameters, the baseline of 4 is appropriate since there's nothing to clarify.
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 'List upcoming scheduled posts' clearly states the verb (list) and resource (scheduled posts), with 'upcoming' distinguishing from possibly past posts. It is not a tautology and effectively differentiates from sibling tools like create_post or cancel_post.
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 is provided on when to use this tool vs alternatives. For example, it does not mention that this tool is read-only or that create_post should be used for creating posts. The description lacks context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a unique resource and action: drafts, scheduled posts, published posts, accounts, analytics, quota, and queue info are all clearly separated. No two tools overlap in purpose; even similar-sounding ones like list_scheduled_posts and list_published_posts are distinct.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_post, list_drafts, get_posting_quota). The use of 'list_' for collections and 'get_' for single items/summaries is predictable and logical.
Tool Count5/5
14 tools is well within the ideal 3-15 range and appropriately covers the domain of social media post management, scheduling, drafts, analytics, and account inspection. Each tool serves a distinct function without redundancy.
Completeness4/5
The surface covers the full lifecycle of posts and drafts: create, read, update, delete, schedule, cancel, and reschedule. Minor gaps exist, such as no direct way to convert a draft into a post, but this can be worked around by copying content.