Skip to main content
Glama

Edit a series

autoshort_update_series
DestructiveIdempotent

Update a series' name, brief, schedule, auto-post flags, madeForKids setting, or AI motion level; only provided fields change.

Instructions

Change a series: name, brief, schedule, auto-post flags, the madeForKids answer or the AI motion level (motionMixLevel). Only the fields you pass change. 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.

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>"
    },
    "name": "autoshort_update_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
briefNo
seriesIdYesSeries id (or slug).
madeForKidsNo
autoPostTikTokNo
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.
autoPostThreadsNoPublish each new video on the connected Threads profile.
autoPostYouTubeNo
autoPostFacebookNoPublish each new video as a Reel on the connected Facebook Page.
autoPostInstagramNoPublish each new video as a Reel on the connected Instagram account.
scheduleIntervalDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the update is free, that active series generate scheduled videos at render time, that insufficient balance or spending cap causes a skipped run rather than failure, and that scheduled videos count against the agent spending cap. It does not clarify the destructive effect of changing a schedule on already-queued videos, which is why it is not a 5.

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 front-loaded with the change operation and the partial-update rule, then moves into scheduling and cost behavior. It is somewhat long, but the scheduling and balance details are relevant for an edit tool that controls an active series.

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

Completeness3/5

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

For an 11-parameter mutation tool with no output schema, the description covers cost, scheduling and spending-cap behavior well. It still lacks return-value expectations, validation behavior, and the effect of schedule changes on existing queued videos, which are material omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 45%, so the description must help compensate. It successfully lists all the editable fields, but adds little semantic detail for undocumented parameters such as scheduleIntervalDays and the auto-post flags; the rich motionMixLevel explanation lives in the schema rather than the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource, 'Change a series', and enumerates the mutable fields including name, brief, schedule, auto-post flags, madeForKids and motionMixLevel. It does not explicitly distinguish itself from create/pause/resume siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a useful partial-update rule ('Only the fields you pass change') and explains ongoing scheduler behavior, but it does not say when to use this versus create_series, pause_series, resume_series, or update_draft. Usage is implied rather than explicitly routed.

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