Skip to main content
Glama

List series

autoshort_list_series
Read-onlyIdempotent

List your autopilot series newest first with schedules, auto-post flags, and brief/video counts; use page and limit to review channels.

Instructions

List the user's series (autopilot channels), newest first, with schedule, auto-post flags, brief and video count. Paginated (page, limit). 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": "autoshort_list_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds real value beyond them by disclosing ordering ('newest first'), the returned fields, pagination, and the absence of credit cost. It omits pagination metadata such as total counts or default page size.

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?

Three compact sentences, all front-loaded and free of filler; each one contributes (scope, returned fields, paging, cost). Sentence fragments like 'Free.' are terse but readable.

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?

There is no output schema, so the description usefully enumerates what each item contains and specifies ordering and paging behavior. For a simple zero-required-parameter read tool with full annotation coverage, that is close to sufficient, with only default page size and total-count behavior left unstated.

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?

With 0% schema description coverage, the description must carry the parameters, and it names both page and limit and frames them as pagination controls. It does not supply defaults or restate the limit maximum of 100, leaving some detail to the schema.

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 ('List the user's series') and disambiguates the domain term with '(autopilot channels)', plus names the fields returned. It doesn't explicitly contrast with siblings like autoshort_get_series_performance or autoshort_list_videos, so it falls just short of a 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?

There is no explicit when-to-use or when-not-to-use statement; usage is only implied by the fact that this enumerates series that other tools mutate. The trailing 'Free' hints that cost-sensitive flows can start here, but that is inference rather than guidance.

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