Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

faceit_clip

Read-only

Get FACEIT Allstar clip detail. Returns one Allstar clip by id: title, view count, embed URL, thumbnail, linked FACEIT match id and match instance, processing status, demo filename, clip reason, map and round. Clip ids come from faceit-clips. An unknown id answers 404.

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": {
      "id": "<id>"
    },
    "name": "faceit_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired 24-character clip id from faceit-clips.

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the failure behavior 'An unknown id answers 404', which is genuinely useful for error handling. It also names the returned fields, which overlaps with the output schema but adds context about the shape of the record.

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 verb and resource, then the id source, then the 404 behavior. The mid-sentence field enumeration is long but scannable and every clause carries information; no filler sentences.

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 one-parameter read with annotations and an output schema, the definition covers purpose, id sourcing, and error behavior. Nothing essential to correct invocation is missing, though a pointer to the list sibling for discovering ids would close the loop.

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 the single parameter already documents the 24-character id sourced from faceit-clips, so the description's 'Clip ids come from faceit-clips' largely restates the schema. Baseline 3 applies since the schema carries the parameter semantics.

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?

Specific verb and resource: 'Get FACEIT Allstar clip detail' followed by 'Returns one Allstar clip by id'. The singular-by-id scope implicitly separates it from list-style siblings like faceit_clips or faceit_best_clips, though it never names an alternative explicitly.

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?

'Clip ids come from faceit-clips' gives the agent the prerequisite and where to source the required id, which is the main usage decision for a lookup tool. It stops short of stating when to prefer a sibling (e.g. match-level or best-clips tools) over this one.

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