Skip to main content
Glama

Plan a posting schedule

schedule_clips_plan

Preview exactly which clips would post to which platforms and when, using a daily budget or fixed hourly gap, without creating or publishing anything—then confirm the plan in the app.

Instructions

Work out what posting a set of clips would do: which clips, which platforms, and the exact time each one would go out. Creates nothing and posts nothing. Give video_id to take every rendered clip from a video, or clip_ids for specific ones. Spacing: per_day for a daily budget ("5 a day" is per_day 5, the default when no spacing is given, because WoopSocial allows about 5 YouTube posts a day), or every_hours for a flat gap (24 is one a day). Always show the result and get a clear yes — the person confirms in the app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "schedule_clips_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_dayNoPosts a day, queued behind what is already scheduled. Defaults to 5 when no spacing is given.
clip_idsNo
hashtagsNoAdded to every clip in the run. The # is optional.
start_atNoRFC 3339 WITH offset. Defaults to now.
video_idNoTake every rendered clip from this video.
gap_hoursNoHours between a day's posts. Defaults to 1.
platformsNoDefaults to youtube. e.g. ['youtube', 'tiktok'].
every_hoursNoA flat gap instead of a daily budget. 1 is hourly, 24 is daily.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states that nothing is created or posted, explains the default per_day value of 5 due to a WoopSocial YouTube posting limit, and notes that the person confirms in the app. It does not describe the return shape or error behavior, but for a preview tool the key behavioral traits are disclosed.

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?

The purpose is front-loaded in the first sentence, followed by the safety constraint, parameter guidance, spacing defaults, and confirmation workflow. Some sentences are longer than necessary, but every part contributes useful operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, annotation-free planning tool with no output schema, the description covers the critical points: side-effect-free behavior, parameter choice, spacing defaults, and the need for user confirmation. It leaves some parameter details to the well-covered schema, which is acceptable.

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?

Schema coverage is high at 88%, so the baseline is 3. The description still adds meaning beyond the schema by explaining the either-or choice between video_id and clip_ids, clarifying that '5 a day' maps to per_day 5 and is the default when no spacing is given, and that every_hours 24 means one a day.

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 first sentence states a specific verb and resource: work out what posting a set of clips would do, including platform and exact timing. The second sentence, 'Creates nothing and posts nothing,' clearly distinguishes this planning tool from the execute sibling schedule_clips_execute.

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?

It tells the agent to use video_id for all rendered clips or clip_ids for specific ones, and describes the spacing choice between per_day and every_hours. It also instructs the agent to show the result and get a clear yes, but does not explicitly name alternative tools or state when not to use this planner.

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