Skip to main content
Glama

Pause a series

autoshort_pause_series
Idempotent

Pause a series to stop scheduled video creation and charges until resumed; existing videos stay untouched. Free.

Instructions

Pause a series: the scheduler stops making (and charging for) its videos until resumed. Videos already made are untouched. Free.

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_pause_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: production and charging halt, existing videos are preserved, and the action is free. This complements idempotentHint and destructiveHint=false by specifying what is and isn't affected, though it does not say what confirmation or response the caller gets.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and its consequence, with no redundant restatement of the title. Every clause carries information: effect, preservation of existing videos, and cost.

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 state-change tool with annotations and no output schema, the definition covers effect, reversibility, side-effect scope, and price. The remaining gap is mechanical: no guidance on sourcing seriesId or on what the call returns to confirm success.

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

Parameters2/5

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

The single required parameter seriesId has 0% schema description coverage, and the description says nothing about it — not where to obtain an ID (e.g., from list_series), not whether it is a slug or opaque ID. The self-explanatory name is the only aid, so the description does not compensate for the coverage gap.

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?

States a specific verb and resource ("Pause a series") and immediately describes the effect: the scheduler stops making and charging for videos. That distinguishes it from make/generate siblings, but the inverse sibling (autoshort_resume_series) is only implied by "until resumed" rather than named.

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?

Clear usage context is given: pause when you want production and billing to stop, and the description notes it is reversible ("until resumed"), which is the key decision criterion versus cancelling. No explicit exclusions or named alternatives, so it stops short of a 5.

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