Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_clips

Retrieves a paginated list of a CS2 player's FACEIT Allstar clips, including clip IDs, titles, views, embed URLs, thumbnails, linked match details, map, round, and processing status.

Instructions

FACEIT player Allstar clips. Returns one page of a player's Allstar clips: clip id, title, view count, embed URL, thumbnail, linked FACEIT match id and match instance, processing status, map, round and creation/update timestamps. Only the cs2 game has Allstar clips; every other game is rejected by the upstream as unknown. Paging uses limit and offset and the response reports has_more. An unknown player 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>",
      "user_id": "<user_id>"
    },
    "name": "faceit_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.
`user_id`	Yes	FACEIT user UUID.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the cs2-only upstream restriction, the limit/offset paging model, that the response reports has_more, and that an unknown player yields a valid empty page instead of an error. Auth requirements and rate limits are not mentioned, 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?

Dense and front-loaded: the first sentence identifies the resource, then return fields, then the game restriction, then paging behavior. The opening fragment 'FACEIT player Allstar clips' is terse but readable, and every sentence contributes 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?

There is no output schema, so the description compensates by enumerating the returned fields and the has_more flag. Combined with the empty-page and game-restriction notes, an agent has enough to call and interpret the tool correctly, though it never says what happens on invalid offsets or how errors surface.

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% and each parameter already has a description, so the schema does the heavy lifting. The description reinforces that paging uses limit and offset and that only cs2 is accepted, but adds no syntax or constraints beyond what the schema states.

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 the specific resource (a single player's Allstar clips) and enumerates the returned fields, so an agent can tell this is a per-player clip listing rather than a global or per-match one. It stops short of naming the sibling tools (faceit_best_clips, faceit_match_clips) that would make the distinction explicit.

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: the phrase 'player's Allstar clips' suggests it applies when a user_id is known, and the cs2-only note rules out other games. There is no explicit statement of when to prefer this over related clip tools, and no mention of prerequisites such as authentication.

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

Deploy Server