Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_match_clips

Retrieve one page of FACEIT Allstar clips for a specific CS2 match, including clip titles, view counts, embed URLs, thumbnails, map and round details.

Instructions

FACEIT Allstar clips for one match. Returns one page of the Allstar clips attached to one FACEIT match: clip id, title, view count, embed URL, thumbnail, linked user and match ids, processing status, map and round. Match ids come from any clip row returned by faceit-clips or faceit-best-clips. Only cs2 has Allstar clips; an unknown match is a valid empty page.

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

Input Schema

Name	Required	Description
`game`	Yes	Game slug; only cs2 has Allstar clips.
`limit`	No	Optional page size, 1-100; default 10.
`offset`	No	Optional non-negative row offset.
`match_id`	Yes	Upstream match id from a clip row, for example 1-bef84e57-4ce3-41aa-b5e5-2918228c1c28.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does so reasonably: it discloses pagination ("one page"), the game restriction, and the important edge case that an unknown match returns a valid empty page rather than an error. It omits ordering, auth expectations, and rate limits, which keeps it short of a 5.

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?

Front-loaded with the purpose, then the payload, then the id-provenance caveat and the empty-page edge case, in three dense sentences with no filler. Slightly list-like in the payload enumeration but every clause carries information.

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?

No output schema exists, so the description compensates by enumerating the returned clip fields (id, title, views, embed, thumbnail, user/match ids, processing status, map, round) — a genuine addition. Combined with the empty-page and cs2 notes, an agent can invoke this correctly; only ordering and total-count behavior are unstated.

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%, so game, limit, offset, and match_id are already documented, including the cs2 enum and the example match id format. The description reinforces match_id provenance and implies limit/offset pagination via "one page" but adds no syntax or format detail beyond the schema — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Returns one page of the Allstar clips attached to one FACEIT match") and names the exact payload fields returned. It also distinguishes itself from the clip-listing siblings by explaining that match ids originate from faceit-clips or faceit-best-clips, so an agent can tell it is a per-match lookup rather than a listing tool.

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?

Gives a clear precondition (match_id must come from a clip row returned by faceit-clips or faceit-best-clips) and a domain restriction (cs2 only). It does not spell out when to prefer this over the sibling clip tools explicitly, but the upstream dependency plus the cs2 constraint effectively routes usage.

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

Deploy Server