Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_clips

Read-only

Get 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

NameRequiredDescriptionDefault
gameYesRequired game slug; only cs2 has Allstar clips.
limitNoOptional page size, 1-100; default 10.
offsetNoOptional non-negative row offset.
user_idYesRequired FACEIT user UUID.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description usefully adds that non-cs2 games fail upstream, that the response reports has_more, and that an unknown player is an empty page rather than a failure. It adds nothing on rate limits, auth requirements, or ordering of results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and constraints are front-loaded, which is good, but the long enumeration of returned fields (clip id, title, view count, embed URL, thumbnail, match id, status, map, round, timestamps) duplicates the output schema and consumes most of the text. Trimming that list would lose no 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?

For a four-parameter, paged read tool with an output schema and annotations in place, the definition covers the game restriction, paging contract, and empty-result semantics that an agent could otherwise get wrong. Only the return-field list is superfluous rather than missing content.

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 both limit and offset already carry descriptions with ranges and defaults, so the description's 'paging uses limit and offset' restates rather than extends. The only extra semantics — that game must effectively be cs2 — is already in the schema field description.

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 first sentence uses a specific verb and resource ('Get FACEIT player Allstar clips') and the second scopes it to a single player's page, which separates it from match-scoped or best-of siblings. It never explicitly names an alternative such as faceit_best_clips or faceit_match_clips, so the differentiation is implied by scope rather than stated.

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 use conditions: only the cs2 game is accepted and other games are rejected upstream, plus how paging works and that an unknown player yields a valid empty page rather than an error. It stops short of any explicit routing advice to sibling clip tools for other scopes.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources