Skip to main content
Glama

Create a series

create_series
Idempotent

Create a series: StoryShort makes a video on this niche every scheduleIntervalDays, and can auto-post it to YouTube. The series NAME is the topic every video is written from, so put the user's own subject in it. Creating or changing a series is FREE. While active, the scheduler makes one video every scheduleIntervalDays (the first at its next run, within about 30 minutes) and charges each video like any video, 40 credits with the default render, at render time. It needs at least 40 credits in the balance: when the balance cannot pay for the next video the scheduler PAUSES the series (it never overdraws), so create_series and resume_series refuse with SERIES_NEEDS_CREDITS instead of making a series that would never run. Agents may keep at most 5 series active at once (SERIES_LIMIT_REACHED). StoryShort has no per-key daily spending cap: pause_series is the brake. Set startPaused: true to create it without generating (then resume_series). Accounts with fewer credits than one video (every new account starts at 0, and free accounts cannot run a series) are refused: you get SERIES_NEEDS_CREDITS with a topUpUrl, nothing is created. autoPostYouTube only works once YouTube is connected (get_connection_status) — nothing checks it here; madeForKids is the COPPA answer, ask the user. A name that already exists returns SERIES_EXISTS. TikTok auto-post is not available for series (use publish_video, which sends to Drafts). Pass idempotencyKey so a retry never makes a second series. Requires the "video:create" scope.

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": {
      "name": "<name>",
      "niche": "<niche>"
    },
    "name": "create_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe series topic/name; every video is generated from it.
nicheYesContent niche (list_niches).
qualityNo
languageNoNarration language code, e.g. "en" (default).
madeForKidsNoCOPPA answer for YouTube uploads from this series. Ask the user.
startPausedNoCreate without generating until resume_series.
idempotencyKeyNoRetry-safe: a repeat with the same key returns the first answer (replayed: true).
autoPostYouTubeNoUpload each finished video to the connected YouTube channel.
defaultDurationNoSeconds per video; longer lengths need a paid plan.
scheduleIntervalDaysNoOne video every N days (default 1 = daily).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only cover the safe/idempotent/mutating profile; the description layers on real behavior the agent cannot infer: 40 credits charged per video at render time, no overdraw (series PAUSES instead), first run within ~30 minutes, a 5-active-series cap, the video:create scope requirement, and the SERIES_NEEDS_CREDITS/SERIES_LIMIT_REACHED/SERIES_EXISTS error contract. The one soft spot is that it says nothing about what the create response returns, though that is partly covered by the idempotency replay note.

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 content is dense and mostly front-loaded — purpose first, then billing, limits, errors, prerequisites. But it is delivered as one long unbroken block, so the pricing, error-code, and prerequisite clusters run together and are harder to scan than they need to be for a tool with this many caveats.

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 10-parameter mutation with no output schema, this covers the hard parts: cost model, pause/overdraw semantics, concurrency cap, auth scope, idempotent retry behavior, and every named failure mode. Nothing an agent needs in order to call create_series correctly appears to be missing.

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 already 90%, so the baseline is 3; the description earns more by adding meaning the schema lacks — that 'name' should contain the user's own subject, that madeForKids is a COPPA answer the agent must ask the user for, and that autoPostYouTube silently does nothing unless YouTube is connected. scheduleIntervalDays and idempotencyKey are explained too, though defaultDuration/quality/language are left 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?

Opens with a specific verb+resource and immediately defines the object: 'StoryShort makes a video on this niche every scheduleIntervalDays, and can auto-post it to YouTube.' The role of the series NAME as the per-video topic is spelled out, which distinguishes it from update_series, resume_series and list_series without requiring a schema read.

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?

Explicitly routes the agent: use startPaused:true then resume_series to create without generating, pause_series is the spending brake, publish_video is the path for TikTok auto-post, and get_connection_status gates autoPostYouTube. It also names the conditions that make the call fail (fewer credits than one video, 5-series cap), which is exactly the when-not guidance an agent needs.

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