Skip to main content
Glama

Plan a batch of uploads

publish_plan

Preview final titles, descriptions and publish times for selected clips before scheduling. Creates nothing, so you can confirm the plan before anything goes live.

Instructions

Work out what publishing these clips would do: final titles, descriptions and publish times. Creates nothing. Give start_at (with a timezone offset) and every_hours to space them out, or neither to upload as soon as each is ready. ALWAYS show the plan and get a yes before executing it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clip_ids": "<clip_ids>"
    },
    "name": "publish_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
privacyNopublic, unlisted or private. Scheduled videos are private until their time.
clip_idsYesClips to publish, from list_clips
start_atNoWhen the first goes out, RFC 3339 with an offset, e.g. 2026-09-18T12:00:00-05:00
every_hoursNoHours between videos, e.g. 1 or 0.5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden. It does disclose the critical non-mutating nature ('Creates nothing') and the content of the result (titles, descriptions, times) — but this is exactly the kind of claim annotations would normally certify, and the score reflects how much rests on description alone. Wait — reassessing: the description does disclose the key trait, so the score should reflect that value.

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?

Three tight sentences, front-loaded with the outcome, then the parameter combinations, then the mandatory confirmation gate. No filler, and the most consequential instruction (show the plan, get a yes) is placed last for emphasis.

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?

With no annotations and no output schema, the description does the heavy lifting well by naming what the plan contains and that nothing is created. It leaves open whether the plan is persisted for the execute step or must be recomputed, which matters for a two-step publish workflow.

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 100%, but the description still adds relational semantics the schema cannot express: start_at and every_hours are meaningful together, and passing neither means immediate publishing. It also reinforces the timezone-offset requirement for start_at. The privacy parameter's behavior is left entirely to the 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?

States a specific verb and resource — working out the result of publishing clips (final titles, descriptions, publish times) — and immediately disambiguates with 'Creates nothing', which separates it from an execute sibling despite the 'publish' prefix. An agent can tell it is a dry-run preview without opening the schema.

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?

Gives concrete usage rules: pass start_at plus every_hours to space uploads, or neither to publish as soon as each clip is ready, plus the workflow gate 'ALWAYS show the plan and get a yes before executing it'. It stops short of naming the execute sibling explicitly, so routing relies on inference from the workflow sentence.

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