Skip to main content
Glama

Resume a series

autoshort_resume_series
Idempotent

Resume a paused series so its scheduler continues creating one video at each configured interval, charging only at render when balance covers it.

Instructions

Resume a paused 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, 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_resume_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare non-read-only, idempotent, non-destructive, open-world, and the description adds genuinely new behavioral facts: per-video charging at render, skip-on-short-balance rather than failure, the ~30 minute first run, and the daily agent spending cap tied to this key. That is strong value beyond structured fields, though the response/return behavior on resume is left unstated.

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 purpose is front-loaded in the first sentence and the following billing rules are information-dense rather than filler, but the 'Creating or changing a series is FREE' clause is only tangential to resuming and slightly dilutes focus.

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?

For a one-parameter mutation with no output schema, the description covers the economics, failure semantics, and scheduling cadence thoroughly. The remaining gap is how to obtain the seriesId and what the call returns, which are minor against the billing detail supplied.

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 0% and the single parameter seriesId is never mentioned in the description, so the description does not tell the agent where a seriesId comes from (e.g., from autoshort_list_series). The name is self-evident, which keeps this at minimum-viable rather than worse.

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 opens with a specific verb and resource ('Resume a paused series'), which distinguishes it cleanly from autoshort_pause_series and autoshort_create_series without the agent needing to open any schema.

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?

The 'paused series' precondition is implied by the verb, and the mention of creating/changing being free hints at the create/update boundary, but no alternative tool is named and there is no explicit when-not guidance (for example, what to do if the series is already active).

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