Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

search_videos

Read-onlyIdempotent

Search OnlyChili's public AI-generated video and drama series catalog by title, localized series name (across all 8 supported languages), or #tag.

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": {
      "query": "<query>"
    },
    "name": "search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching public videos to return (1-25).
queryYesSearch phrase, localized series title across any of the 8 supported languages (e.g., 'Lingerie Office', 'Bureau en Dentelle', 'Oficina de Lenceria'), or #tag.
localeNoPreferred display locale for returned titles and canonical URLs.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds that only public content is searched and that localized names across 8 languages are supported, but it says nothing about result ordering, pagination behavior, or empty-result handling.

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?

The definition is a single front-loaded sentence with no wasted wording. It efficiently conveys the resource, scope, and searchable dimensions, though it could add a brief note about result behavior.

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 straightforward search tool with complete parameter documentation and clear read-only annotations, the definition is largely complete. The only meaningful gap is that it does not describe result behavior or clarify search versus listing alternatives.

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 query, limit, and locale are already well documented in the input schema. The description reinforces the multi-language searchable fields but adds no syntax, matching behavior, or tag-format detail beyond 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?

The description states a specific verb and resource: search OnlyChili's public AI-generated video and drama series catalog. It clearly identifies the searchable fields (title, localized series name, #tag) and the public scope, though it does not explicitly distinguish itself from siblings such as list_series or list_latest_videos.

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 implied by the presence of a search phrase, localized series name, or #tag, so an agent can infer when to use it. However, there is no explicit when-not guidance and no named alternative for browsing versus searching.

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