Skip to main content
Glama

List series

list_series
Read-onlyIdempotent

List the user's series (autopilot channels), newest first, with schedule, auto-post flags, active/paused state, credits per video and an estimate per month. Paginated (page, limit). Requires the "video:read" scope. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value on top: result ordering (newest first), the exact field set returned, pagination behavior, the required 'video:read' scope, and that the call is free. What it omits is the default page size and whether a total count is returned.

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 tight sentences with zero filler, and the core purpose plus result ordering are front-loaded. Every clause adds information: resource definition, return fields, pagination, scope, 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?

With no output schema, the description responsibly lists what is returned, and it covers auth scope, cost, and ordering. For a simple two-optional-parameter list tool this is nearly complete; the missing pieces are pagination defaults and how to detect the last page.

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 0%, so the description carries the burden for both parameters. It only labels them collectively as 'Paginated (page, limit)' without stating defaults, the 1-100 limit range, or what happens when they are omitted; the bounds exist in the schema but are undocumented. It does at least identify the parameters' role, so it is not a total 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?

The description pairs a specific verb (List) with a specific resource (the user's series) and even disambiguates the term by glossing it as 'autopilot channels', which separates it from list_videos and list_niches. It also enumerates the fields returned (schedule, auto-post flags, state, credits, monthly estimate). It stops short of explicitly naming a sibling to differentiate from, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is the enumeration call for autopilot channels, and 'Free' signals there is no credit cost to calling it. There is no explicit when-to-use guidance and no mention of alternatives such as get_series_performance for metrics or create_series for creation.

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