Skip to main content
Glama

Schedule a whole series in order

clipember_schedule_series
Idempotent

Queue every part of a SERIES (a request created with series=true) to the chosen platforms in story order, one part every gapMinutes starting at startAt. Each part shows 'PART n/N' on screen and 'Part n of N' in its caption; a part never goes out before the previous one. TikTok is not supported for series yet (parts would land in the Inbox and need publishing by hand). Every part of a platform goes to one account: if the user has several connected accounts on a platform, ask which one and pass it in connectionIds (ids from clipember_list_platform_connections) — without it the call is refused rather than guessing. Already-queued parts are skipped, so calling it twice does not duplicate the series. This WILL publish publicly later.

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": {
      "seriesId": "<seriesId>",
      "platforms": "<platforms>",
      "startAt": "<startAt>"
    },
    "name": "clipember_schedule_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
startAtYesWhen Part 1 goes out (ISO 8601)
seriesIdYesseries.id from clipember_get_clip_request
platformsYes
gapMinutesNoMinutes between parts (default 180)
connectionIdsNoWhich account each platform's parts go to — required for a platform with several connected accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / connectionIds
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which account each platform's parts go to — required for a platform with several connected accounts",
      +  "properties": {
      +    "instagram_reels": {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    },
      +    "youtube_shorts": {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses that content will publish publicly later, parts are ordered and never go out before the previous one, TikTok parts would land in the Inbox, and missing account selection is refused rather than guessed. It also confirms idempotent behavior by explaining repeated calls skip already-queued parts.

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?

The description is front-loaded with the core scheduling action and then layers in constraints in a logical order. Every sentence conveys operational detail, and none is redundant.

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?

For a complex mutation with account-selection branching and public publishing consequences, the description covers ordering, timing, platform limits, idempotency, and failure conditions. No output schema exists, but the description still tells the agent enough to invoke the tool correctly.

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?

The schema already covers most parameters, but the description adds meaningful semantics for connectionIds: where IDs come from, when to ask the user, and that the call is refused without them. It also clarifies that startAt controls Part 1 and gapMinutes spaces subsequent parts.

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 description states a specific verb and resource: queue every part of a SERIES to chosen platforms in story order. It defines what a SERIES is (a request created with series=true), which clearly distinguishes this tool from scheduling ordinary clips.

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?

It gives explicit operational guidance: TikTok is unsupported, multiple connected accounts on a platform require asking the user and passing connectionIds, and omitting connectionIds causes refusal. It also references clipember_list_platform_connections for obtaining account IDs and explains that already-queued parts are skipped.

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