Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

list_series

Read-onlyIdempotent

List public serialized AI drama playlists on OnlyChili with 8-language titles, canonical playlist URLs, episode counts, and creator handles.

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
limitNoMaximum number of public series playlists to return (1-25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered by structured data. The description adds that results carry 8-language titles, canonical URLs, episode counts, and creator handles, which is helpful context not found elsewhere. It says nothing, however, about ordering, pagination, or what an empty result means.

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?

One front-loaded sentence with a specific verb, scope, and field list; every clause carries information and there is no filler or redundancy.

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 simple read-only, single-parameter list tool with annotations and complete parameter documentation, the description covers purpose and return content adequately. The one meaningful gap is result ordering, since it never says whether playlists come back by recency, popularity, or another order.

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?

There is a single parameter and schema description coverage is 100%, with 'limit' documented as 1-25 defaulting to 10. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 public serialized AI drama playlists on OnlyChili', plus the fields returned. It is clearly distinct from get_video or get_channel in substance, but never names or contrasts with the sibling listing/search tools, so differentiation is left to the agent.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as search_videos or list_latest_videos. The agent must infer from its own knowledge that this tool is for browsing public series playlists rather than searching or fetching a single item.

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