Skip to main content
Glama

Pause a series

pause_series
Idempotent

Pause a series: the scheduler stops making (and charging for) its videos until resume_series. Videos already made are untouched. Requires the "video:create" scope. 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": "pause_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesSeries id (or slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that billing stops, that existing videos are preserved (a non-destruction guarantee that reinforces destructiveHint=false), the required 'video:create' scope, and that the call is free. Those are exactly the facts an agent needs before invoking a mutation on a paid pipeline.

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?

Four short sentences, front-loaded with the action and effect, then the preservation guarantee, then prerequisites and cost. No filler and nothing repeated from the title.

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 one-parameter mutation with no output schema, the description covers effect, side effects on existing data, authorization scope, and cost, leaving no obvious question an agent would need answered before calling it.

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 documented there as 'Series id (or slug)'. The description adds nothing about the identifier format, so the baseline of 3 applies.

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?

Specific verb plus resource ('Pause a series') followed immediately by the concrete effect: the scheduler stops making and charging for videos. It is clearly distinguishable from resume_series, which is named as the counterpart action.

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 'until resume_series' clause tells the agent this is a reversible, temporary halt and points at the inverse tool. It does not explicitly state when NOT to use it (e.g., for permanent cancellation, which cancel_video or update_series might cover), so it stops short of a full routing rule.

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