Skip to main content
Glama

Schedule post

schedule_post
Destructive

With post_id and remove: true, remove a finished or canceled post from Kuro's calendar and Needs attention only. Published social-media posts and analytics remain intact. Cancel scheduled posts first; sending posts cannot be removed until they finish. Removal cannot be combined with other edits. Create, edit or withdraw a post to the reader's connected social accounts. Without post_id it creates one from a ready image, clip or image set in the account (generation_id) or a verified upload (upload_id) — exactly one — with a caption, one target per account and the reader's IANA timezone; title is required when a target is YouTube. With post_id it edits that post — send only what changes — and with post_id and cancel: true it withdraws a draft or a scheduled post. Timing is one of three. scheduled_for (an ISO time, two minutes to ninety days ahead) schedules it. Neither scheduled_for nor post_now makes a DRAFT on create — nothing goes out, and the reader finds it in the calendar's drafts; on an edit it leaves the timing alone, and draft: true takes a scheduled post's time away. post_now: true sends it immediately and needs the social.publish_now permission, which a connection holds only when the reader granted it; use it only when the reader asked for the post to go out now. Draft and propose; schedule on the reader's go-ahead. A post to three accounts is ONE post with three targets. Each target carries that platform's options (start from the account's last_options in list_social_accounts, the reader's previous answers) and may carry its own caption when the platforms want different words. An edit's targets replaces the whole list. Accounts are connected only in the app, at /settings/social.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNo
titleNo
cancelNoWith post_id: withdraw the draft or scheduled post.
removeNoWith post_id only: remove a finished or canceled calendar entry, keeping published social-media posts.
captionNo
post_idNoThe post to edit or withdraw. Omit to create one.
targetsNo
post_nowNo
timezoneNoThe reader's IANA time zone, such as Europe/Paris — the calendar shows the post in it. Required on create.
upload_idNoCreate only, instead of generation_id: the verified uploaded image or clip to post, from list_media.
generation_idNoCreate only: the ready image, clip or image set to post, from list_media.
scheduled_forNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint/openWorld/not-idempotent, and the description goes well beyond them: it discloses exactly what removal destroys (only the calendar entry and Needs attention, with published posts and analytics intact), the required social.publish_now permission and when a connection holds it, and the constraint that removal is incompatible with other edits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading the removal edge case before the primary create/edit flow is a slight ordering weakness, and the four paragraphs are dense. However, nearly every sentence conveys distinct operational detail, so the length is largely justified by the tool's complexity.

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?

An output schema exists so return values need not be explained, and the description covers all three timing modes, target-per-account semantics, the create/edit/cancel/remove branching, permission requirements, and where accounts get connected. Nothing an agent needs to invoke it correctly is missing.

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?

At 50% schema coverage the description carries real weight: it explains that generation_id/upload_id are mutually exclusive ('exactly one'), timezone is required on create, title is required when a target is YouTube, scheduled_for accepts two minutes to ninety days ahead, and that targets replaces the whole list on edit while options should seed from last_options.

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 specific verbs and resource (create, edit, withdraw, remove a post to the reader's connected social accounts) and distinguishes the create/edit/cancel/remove modes by their key parameter combinations. An agent can tell it apart from list_posts and list_social_accounts, which it explicitly references as data sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when/when-not guidance: 'use it only when the reader asked for the post to go out now', 'Draft and propose; schedule on the reader's go-ahead', 'Cancel scheduled posts first; sending posts cannot be removed until they finish', and 'Removal cannot be combined with other edits'. These are concrete operating rules, not vague hints.

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.

Resources