Skip to main content
Glama

list_highlights

Read-only

Retrieve ranked CS2 match highlights with scores, tiers, and video links; filter by player, category, or featured status to review standout plays or fails.

Instructions

Highlights of a match, best first, with video URL when rendered. score is 0-100 and tier S/A/B/C; featured plays are the curated best of each team plus stand-out plays - they get first-person videos, the others only 2D replays. get_highlight shows the score breakdown (feat, impact, style, economy, stakes, outcome). Pass featured=true for just the curated ones.

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": "list_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
playerNo
categoryNofail = the match's fails (whiffs, team flashes, team kills…).play
featuredNo
match_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a safe read with no open-world access. The description adds useful behavior beyond that: ordering best-first, video URLs only when rendered, first-person video for featured plays versus 2D replays otherwise, and the 0-100 score/tier scale. That is strong added context, though it omits pagination behavior for limit.

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?

Three dense sentences, front-loaded with the resource and ordering, then semantics, then the featured shortcut. Semicolons pack in a lot of information without much waste, though the middle sentence is somewhat overloaded.

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

Completeness3/5

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

An output schema exists, so the description need not document return fields, and annotations cover safety. For a six-parameter filtered list, however, it leaves player, limit, and kind unexplained, which is a meaningful gap. It is adequate but not complete.

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 only 17%, so the description must carry most parameter meaning. It explains featured well and indirectly clarifies that score and tier describe results, but it says nothing about player, limit, or kind. Several of the six parameters remain opaque beyond their bare schema types.

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 resource and scope, "Highlights of a match," and states the ordering, "best first." It also distinguishes itself from get_highlight by assigning the score breakdown to that sibling. The missing explicit verb (list) is minor because the resource and scope are unambiguous.

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

Usage Guidelines4/5

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

It gives concrete selection guidance: pass featured=true for curated highlights, and use get_highlight for the score breakdown. It does not cover when to prefer other list tools or when not to use this one, but the key alternative is named.

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