Skip to main content
Glama

Change a series' end card

series_end_card
Destructive

Changes a video series' end card, the short card every episode of the series ends on, as the series' page in Create does. make_new: its own card goes, and its next episode makes a new one in the series' look (episodes already made keep theirs). use_brand: its episodes end on the brand's end card instead. use_own: they end on the series' own card, made with the next episode when it has none. ask_ai: puts making it on the owner's own AI's homework list (homework for their AI must be on). The owner's own video is uploaded on the series' page; an AI on the owner's machine sends it with get_upload_link kind endcard and series. A card is made inside the next episode's run, within that episode's own budget, never as a charge of its own. Change it only when the owner asked for this change.

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": {
      "action": "<action>"
    },
    "name": "series_end_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesmake_new: its own card goes and the next episode makes a new one. use_brand: its episodes end on the brand's card. use_own: they end on its own (made with the next episode when it has none). ask_ai: the owner's own AI is asked to make it, on its homework list.
seriesNoThe series' id or exact name. Leave out when the business has one video series.
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The annotations already mark the tool as destructive and not read-only, and the description adds substantial context beyond them: make_new removes the existing card, already-made episodes keep theirs, card creation happens inside the next episode's budget, and AI uploads use get_upload_link with kind endcard. It also states that ask_ai requires the owner's AI homework feature to be on.

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 uses run-on fragments such as 'make_new: its own card goes.' The action explanations repeat schema content and make the description harder to scan than necessary.

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 destructive mutation with no output schema, the description covers the key effects, action modes, budget behavior, and upload path. It does not explain the response format or explicitly state permission requirements, but it is otherwise complete enough to call the tool correctly.

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 description coverage is 100%, so the input schema already documents all three parameters, including the action enum. The description largely restates the action meanings already present in the schema and adds no new syntax or format details for series or project.

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?

The description states a specific verb and resource: 'Changes a video series' end card.' It also explains what an end card is and what each action does. It does not explicitly name the read sibling, but the mutation verb and detailed action breakdown make the purpose clear.

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?

It gives a clear usage constraint: 'Change it only when the owner asked for this change.' Each action is explained, including the prerequisite that homework for the owner's AI must be on. It does not explicitly compare itself with series_end_card_read, but the when-to-use condition is strong.

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.