Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

faceit_best_clips

Retrieve a FACEIT player's best Allstar CS2 clips within a required RFC3339 time window, ranked by upstream best-clip order. Returns an empty list when no clips exist in the range.

Instructions

FACEIT player best clips in a time window. Returns a player's best Allstar clips inside an inclusive time window: the same clip row shape as faceit-clips, ordered by the upstream best-clip ranking. Both from and to are required RFC3339 timestamps. Only cs2 has Allstar clips; a window with no clips is a valid empty list. The upstream ignores offset on this route, so no offset parameter is exposed.

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "faceit_best_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesInclusive upper bound as an RFC3339 timestamp.
fromYesInclusive lower bound as an RFC3339 timestamp.
gameYesGame slug; only cs2 has Allstar clips.
limitNoOptional page size, 1-100; default 10.
user_idYesFACEIT user UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 full burden and does well: it discloses the upstream best-clip ordering, the empty-list semantics, the cs2-only restriction, and that offset is ignored upstream (hence unexposed). It does not cover auth requirements or rate limits, but the key behavioral surprises are surfaced.

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 purpose, then constraints in a sensible order, and every sentence carries information. The opening two sentences overlap slightly ('best clips in a time window' / 'best Allstar clips inside an inclusive time window'), a minor redundancy.

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, but the description compensates by pointing at faceit-clips for clip row shape and by characterizing ordering and empty results. Combined with full schema coverage, an agent has enough to call it correctly; only return-field specifics remain indirect.

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 all five parameters already carry descriptions, and the description largely restates the inclusive RFC3339 requirement for from/to. The one genuine addition is the explanation that no offset parameter exists because upstream ignores it, which exceeds the schema.

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+resource ('Returns a player's best Allstar clips') and scopes it to a time window. It also pins down its relationship to faceit-clips ('the same clip row shape as faceit-clips') and distinguishes best-ranked clips from the general clip siblings.

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 clear contextual constraints for use: both from and to are required, only cs2 produces Allstar clips, and an empty window is a legitimate result rather than an error. It stops short of explicitly naming when an agent should pick faceit_clips or faceit_match_clips instead.

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

Deploy Server

Other Tools