Skip to main content
Glama

Create a series

autoshort_create_series

Create a recurring short-video series that generates one video on a set niche every chosen interval and can auto-post each release to connected social platforms.

Instructions

Create a series: AutoShort makes a video on this niche and brief every scheduleIntervalDays, and can auto-post 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, at render — only when the balance covers it; a short balance skips that run, it never fails or overdraws. A series created or resumed through this connection counts each scheduled video against this key's daily agent spending cap (autoshort_get_limits); over the cap, that day's run is skipped. brief is what the generator writes from (topics, facts, tone) — put the user's own words here. Set startPaused: true to create it without generating yet (resume with autoshort_resume_series). Auto-post needs the platform connected (autoshort_get_connection_status); TikTok auto-post goes to Drafts.

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": "autoshort_create_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
briefNoWhat every video in this series is about — the generator writes from this.
nicheYes
qualityNo
voiceIdNoA voice id from autoshort_list_options (premium voices cost extra per video).
languageNoBCP-47 narration language, or "auto" (default).
madeForKidsNoCOPPA answer for YouTube uploads from this series. Ask the user.
startPausedNoCreate without generating until resumed.
autoPostTikTokNoSends each video to the creator's TikTok Drafts.
motionMixLevelNoAI motion: some scenes of every video are animated with Seedance, the rest stay images; each video is still a complete multi-scene video with voice and captions, never a single clip. Default NONE. Price per video at 30 s: NONE 40 credits per video; HOOK up to 140 credits per video (1 animated scene); HIGHLIGHTS up to 340 credits per video (3 animated scenes); CINEMATIC up to 540 credits per video (5 animated scenes). Animated scenes whose clip cannot start fall back to stills and are not charged. Accounts that have not paid yet can use only NONE or HOOK. If a run cannot afford or start the chosen level it makes the normal NONE video instead.
autoPostYouTubeNo
defaultDurationNoSeconds per video; 90 needs a paid plan.
scheduleIntervalDaysNoOne video every N days (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: creation is free, videos are charged at render, insufficient balance skips a run without failing or overdrawing, scheduled runs count against the daily agent spending cap, and the first run occurs within about 30 minutes. It also explains TikTok Drafts behavior for auto-posting, consistent with the non-destructive, open-world annotations.

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 description is a dense single paragraph but front-loads the core action before billing and operational caveats. The length is largely justified for a 13-parameter scheduling tool, though line breaks or shorter sentences would improve scanning.

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?

Covers the operational essentials an agent needs for a complex scheduler: billing, cap enforcement, pause/resume, connection prerequisites, and auto-post destination. It does not describe the return value, such as the created series identifier, and no output schema exists to fill that gap.

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?

With schema coverage at 69%, the description adds useful meaning for key parameters: brief is what the generator writes from and should contain the user's own words; startPaused defers generation; scheduleIntervalDays controls one video every N days; auto-post depends on a connected platform. It leaves name, quality, language, and madeForKids mostly to the schema, but adds cross-parameter billing and cap context.

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 ('Create a series') and explains the core behavior: AutoShort makes a video from the niche and brief every scheduleIntervalDays and can auto-post it. This clearly distinguishes creation from resume, pause, and update siblings.

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 practical routing: use startPaused to create without generating, resume with autoshort_resume_series, check autoshort_get_connection_status before auto-posting, and check autoshort_get_limits for agent caps. It does not explicitly say when to use autoshort_update_series instead of creating, but otherwise provides strong context.

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