Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

list_latest_videos

Read-onlyIdempotent

List recent publicly published AI-generated videos on OnlyChili with 8-language titles, canonical watch URLs, creator channels, durations, ratings, and access modes.

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_latest_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOptional category or tag filter (for example: drama, anime, realistic, fantasy).
limitNoMaximum number of public videos to return (1-25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: results are restricted to public videos, and each item carries 8-language titles, canonical watch URLs, channels, durations, ratings, and access modes — material since no output schema exists. It omits pagination behavior (only a hard limit of 25 is knowable from the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: verb, resource, scope, then the payload enumeration. The trailing list is long but earns its place because there is no output schema to describe return fields.

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 two-parameter listing tool with full schema coverage and no output schema, the definition covers purpose, scope, and return contents adequately. The remaining gap is the absence of sibling routing guidance (versus search_videos) and any note on paging beyond the 25-item cap.

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 coverage is 100%, and both parameters (tag, limit) are fully documented in the schema, so baseline 3 applies. The description adds no syntax or semantics beyond what the schema already states, though "recent" loosely implies the limit controls recency depth.

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 names a specific verb and resource ("List recent publicly published AI-generated videos on OnlyChili") and adds a scope qualifier (recent, public) that separates it from a general search. It does not explicitly distinguish itself from siblings like search_videos or list_series, so the agent still has to infer the boundary.

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: "recent publicly published" signals a browse-newest-public-videos use case, and the tag parameter hints at category narrowing. There is no explicit statement of when to prefer this over search_videos, and no exclusions or prerequisites.

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