Skip to main content
Glama
jors7

kadenzo-mcp

schedule_post

Schedule social posts for future automatic publishing across multiple connected accounts. Use validate_only to check without scheduling.

Instructions

Schedule a social post to one or more connected accounts for a FUTURE time (it publishes automatically). Set validate_only=true to check accounts/limits/timing without scheduling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadNoMulti-post threads, e.g. {"x":["1/…","2/…"],"bluesky":["…"]}.
contentNoPost text. Optional only if media_urls is provided.
optionsNoPer-platform format options, e.g. {"instagram":{"as_reel":true,"first_comment":"#tags"},"tiktok":{"privacy_level":"PUBLIC_TO_EVERYONE"}}.
media_urlsNoPublic image/video URLs, or URLs returned by upload_media.
account_idsYesAccount ids from list_accounts (at least one).
scheduled_forYesISO 8601 future datetime, e.g. "2026-07-02T09:00:00Z".
validate_onlyNoIf true, validate only (dry run) and do not schedule.
platform_contentNoPer-platform text overrides, e.g. {"twitter":"shorter text"}.
Behavior3/5

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

Describes scheduling for future time and automatic publishing, but lacks details on permissions, rate limits, error handling, or post-validation behavior. No annotations to supplement.

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?

Two sentences, no redundancy, key info front-loaded. Every sentence adds value.

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?

With 8 parameters, nested objects, and no output schema, the description is concise but omits return values, failure modes, and edge cases. Adequate but not fully complete.

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 coverage is 100% so baseline is 3. Description adds context for validate_only, but doesn't enhance understanding of other parameters beyond schema.

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?

Clearly states verb 'schedule' with resource 'social post' and specifies future time and automatic publishing. Distinguishes from sibling tools like cancel_post and get_post.

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

Usage Guidelines3/5

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

Implies usage for scheduling future posts and mentions validate_only for dry runs, but does not explicitly state when not to use or alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jors7/kadenzo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server