Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

get_video

Read-onlyIdempotent

Fetch full metadata, 8-language titles/descriptions, and canonical watch URLs for a single publicly visible video by UUID.

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": {
      "id": "<id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVideo UUID from /watch/{id}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral constraint — only 'publicly visible' videos are retrievable — plus a preview of returned artifacts, but says nothing about failure behavior for private/removed videos or rate limits.

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 sentence, zero filler, scoping constraint ('single publicly visible') front-loaded before the payload list. Every clause carries information an agent can act on.

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 one-parameter read tool with rich annotations and no output schema, the description covers what it returns and the visibility constraint, which is close to sufficient. 'Full metadata' remains vague — the agent cannot tell exactly which fields come back — but no critical calling information is missing.

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?

There is a single parameter and schema coverage is 100%, with the schema already explaining the UUID format sourced from /watch/{id}. The description reinforces the constraint with 'by UUID' and 'publicly visible', adding modest but real meaning about which IDs are valid.

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 gives a specific verb ('Fetch') and a precisely scoped resource ('a single publicly visible video by UUID'), and enumerates the returned artifacts (metadata, 8-language titles/descriptions, canonical watch URLs). This implicitly separates it from list_* and search_videos, though no sibling is named explicitly.

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: 'by UUID' tells the agent it needs a known video identifier, which contrasts with the search/list siblings by construction. There is no explicit when-to-use/when-not statement and no pointer to an alternative for looking up a video when the ID is unknown.

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