schedule_post
Schedule a draft variant for a moment in time.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| timezone | No | ||
| variant_id | Yes | ||
| scheduled_at | Yes | ISO 8601 |
Cadencz
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without mentioning side effects, prerequisites, state changes, or reversibility. For a mutating tool, this leaves critical behavior opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words, but it is so sparse that it borders on under-specification. It is concise in form yet lacks the operational detail needed for an agent to use the tool correctly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 3 parameters, no output schema, and no annotations, the description is incomplete. It omits timezone semantics, the lifecycle of the scheduled post, and how this relates to sibling tools such as publish_now or cancel_scheduled_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?
Schema description coverage is only 33%, so the description must compensate. Phrases like 'draft variant' and 'moment in time' map conceptually to variant_id and scheduled_at, adding some meaning, but the timezone parameter is entirely unexplained.
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?
The description uses a specific verb ('Schedule') and identifies the resource ('draft variant') and temporal qualifier ('moment in time'), making the tool's basic function clear. It implicitly distinguishes itself from publish_now and cancel_scheduled_post, though it doesn't explicitly name an alternative.
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?
The description provides no guidance on when to use this tool versus alternatives like publish_now or cancel_scheduled_post. There are no prerequisites, exclusions, or context hints to help an agent decide correctly.
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
B3.4/5.0
Disambiguation5/5
Each tool targets a distinct action or resource: plan approval, scheduling, publishing, analytics, planning, and listing all have clear boundaries. Even the schedule/publish/approve tools are easy to distinguish because their source objects and outcomes are explicitly different.
Naming Consistency4/5
The naming almost uniformly follows a verb_noun snake_case pattern, such as list_brains, compose_post, and cancel_scheduled_post. The one small deviation is publish_now, which uses an adverb rather than a noun object, but the overall pattern remains highly predictable.
Tool Count5/5
14 tools is well within the ideal range for a content planning and social media scheduling server. Each tool addresses a meaningful part of the workflow without unnecessary bloat or redundant helpers.
Completeness3/5
The tool surface covers planning, composing, scheduling, publishing, canceling, analytics, and workspace/channel context. However, there are notable lifecycle gaps: no update or delete operation for drafts or scheduled posts, and no way to fetch a single post's detail beyond a list.