Skip to main content
Glama

Update a series

update_series
DestructiveIdempotent

Change a series: how often it runs, YouTube auto-post, the madeForKids answer or the language. Only the fields you pass change. The name and niche cannot be changed (create a new series). Making an ACTIVE series run more often raises its spend, so it goes through the same credit check as resume_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": "update_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
seriesIdYesSeries id (or slug) from list_series.
madeForKidsNo
autoPostYouTubeNo
scheduleIntervalDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=true, idempotent=true, openWorld=true, and the description adds genuinely non-derivable behavior: partial-update semantics ("Only the fields you pass change"), free mutation, credit/spend consequences of raising frequency, scheduler timing (~30 min first run), a 5-active-series limit, and the required "video:create" scope. It stops short of saying what the call returns or what happens to an in-flight scheduled video when the interval changes.

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 mutable-field list is helpfully front-loaded, but the middle of the description drifts into a general credit-policy lecture covering create_series, resume_series, pause_series, and SERIES_NEEDS_CREDITS that is largely about sibling tools rather than this one. Much of the 40-credits/overdraft/day-cap material could be compressed to the single relevant fact: raising frequency on an active series costs more and requires balance.

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 five-parameter mutation with no output schema, the definition covers the important traps: partial update, immutability of name/niche, spend impact, limits, and required scope. It leaves the response shape and any validation errors for bad interval or language values unspecified, which is the main remaining gap.

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

Parameters4/5

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

Schema coverage is only 20% (just seriesId), so the description must compensate and mostly does: it names all four optional fields and attaches real meaning to scheduleIntervalDays by explaining the downstream spend and the one-video-per-interval scheduling. It does not explain accepted language formats (maxLength 10 suggests an ISO code) or the effect of autoPostYouTube/madeForKids beyond their literal names.

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?

"Change a series: how often it runs, YouTube auto-post, the madeForKids answer or the language" names a concrete verb, resource, and the exact set of mutable fields, mapping one-to-one onto the optional schema properties. It also draws the boundary against create_series by stating name and niche cannot be changed here.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this to modify an existing series, create a new one for name/niche changes, and pause_series is the brake for spending. It also flags that a frequency increase on an ACTIVE series triggers the same credit check as resume_series, so the agent knows the preconditions before calling.

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