Skip to main content
Glama

Resume a series

resume_series
Idempotent

Resume a paused series. Refused with SERIES_NEEDS_CREDITS when the balance cannot pay the next video, and with SERIES_LIMIT_REACHED at 5 active series. 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. 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": {
      "seriesId": "<seriesId>"
    },
    "name": "resume_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesSeries id (or slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses that resuming triggers recurring credit charges at render time, that the scheduler pauses automatically on insufficient balance rather than overdrawing, and that the first video runs within about 30 minutes. It also names the two failure codes (SERIES_NEEDS_CREDITS, SERIES_LIMIT_REACHED) and the required video:create scope, which an agent cannot infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is dense and repetitive: SERIES_NEEDS_CREDITS and the 40-credit requirement are each explained twice, and the free-vs-charged distinction is restated. The cost and limit facts are valuable but could be stated in roughly half the words.

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 mutation tool with real side effects (spending credits, starting a scheduler), no output schema, and one simple parameter, the description covers cost, cadence, failure modes, hard limits, the absence of a per-key daily cap, and required auth. Nothing material an agent needs to call it safely is missing.

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 coverage is 100% and the single seriesId parameter is already documented as accepting an id or slug, so the description adds no parameter-level meaning. Baseline 3 is appropriate since the schema carries the burden here.

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 opening sentence gives a specific verb and resource ("Resume a paused series"), which directly distinguishes it from pause_series and create_series in the sibling list. The precondition of being paused is stated up front rather than buried.

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?

The description makes clear this applies only to an already-paused series and contrasts create_series/resume_series behavior against the pause_series brake. It stops short of an explicit "use X instead when Y" routing statement, but the context is unambiguous.

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