Skip to main content
Glama

render_reel

Combine multiple match highlights into one video with title cards, using an explicit highlight order or letting the server select the top highlights, optionally for a single player.

Instructions

Render a reel: several highlights back to back in one video, with title cards. Pass highlight_ids for an explicit order, or let the server pick the top best (optionally only for one player).

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": {
      "match_id": "<match_id>"
    },
    "name": "render_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
topNo
extraNo
titleNo
widthNo
heightNo
playerNo
match_idYes
rendererNo
wait_secondsNo
highlight_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the operation is not read-only, not destructive, and closed-world; the description adds that the server can choose top highlights and that title cards are included. However, it does not disclose async/job behavior, the role of wait_seconds, or other side effects beyond annotations.

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?

Two tight sentences with the core operation and selection logic front-loaded. There is no redundant wording, and the alternate selection paths are stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter render tool with a required match_id, a single short description covering only selection controls is not enough. Output schema exists, but key rendering options like fps, dimensions, renderer, wait_seconds, title, and extra remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 11 parameters, so the description must compensate but only explains highlight_ids, top, and player. It leaves match_id, fps, extra, title, width, height, renderer, and wait_seconds without meaning beyond their names.

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 ("Render a reel") and explains the reel is several highlights back to back with title cards. This implicitly distinguishes it from single-highlight rendering, though it does not name a sibling tool for direct comparison.

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?

Explains two selection modes: pass highlight_ids for explicit order, or let the server pick the top best, optionally filtered by player. It does not state when to choose this over render_highlight or when not to use a reel, so usage guidance is partial.

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