get_queue_info
The posting schedule (timezone + weekly slots) and the next open queue slots, i.e. when a create_post with queue=true would actually publish.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Postlia
by com.postlia
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the disclosure burden. It clearly explains what information is returned (schedule and next queue slots) and their interpretation. It does not mention side effects, but this is a read-only info tool, and the description is sufficient.
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, well-structured sentence that front-loads the core content and adds a clarifying example. No wasted words.
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 there are no parameters and no output schema, the description fully explains what the tool returns and its significance. It's complete for the tool's simplicity.
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?
The tool has zero parameters, so the baseline is 4. The description appropriately adds no parameter information since none exist.
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 provides the posting schedule (timezone + weekly slots) and the next open queue slots, with an explicit tie to when a queued post would publish. This distinguishes it from siblings like list_scheduled_posts or get_posting_quota.
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?
The description implies when to use this tool by referencing 'create_post with queue=true', which tells the agent this is useful for planning queued posts. It doesn't explicitly state alternatives or exclusions, but the context is clear.
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.