Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

faceit_hub_memberships

Retrieve a FACEIT user's hub and competition memberships, including role names, join dates, and hub IDs for discovery, with paging and optional category filtering.

Instructions

FACEIT user hub memberships. Returns one page of a user's hub and competition memberships: membership id, user identity, the competition/hub reference (game, category, skill band, join permissions, player count, child ids), role names, highest role ranking and join date. This is the only anonymous hub-discovery path the FACEIT website exposes, so hub ids for faceit-hub come from here. category is a closed enum.

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": {
      "user_id": "<user_id>"
    },
    "name": "faceit_hub_memberships"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional page size, 1-50; default 20.
`offset`	No	Optional non-negative row offset.
`user_id`	Yes	FACEIT user UUID.
`category`	No	Optional hub category; one of community, chat or ihl.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that results are paginated ('one page'), what each row contains, and that the path is anonymous (no auth implied). It says nothing about rate limits, behavior on an unknown or invalid user_id, empty-result semantics, or ordering of rows, which are material for a discovery tool.

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?

Three sentences with the purpose front-loaded, followed by return contents and then the discovery-path caveat. The long parenthetical field inventory is dense but each item corresponds to real returned data; there is little filler.

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 listing the returned fields is necessary and done thoroughly, and pagination plus the enum constraint are covered. The gap is operational behavior (auth expectations beyond 'anonymous', error and empty-result handling) for a tool with four parameters and no annotations.

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 description coverage is 100%, so limit, offset, user_id and the category enum are already fully documented in the schema. The description adds only the framing that the enum is closed and that limit/offset produce one page, which is marginal beyond the structured data. Baseline 3 applies.

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 a specific verb and resource ('Returns one page of a user's hub and competition memberships') and enumerates the payload (membership id, user identity, competition reference, role names, join date). It also positions itself against the hub-lookup siblings by noting hub ids for faceit-hub come from here, though it never names faceit_hubs or faceit_hubs_detailed explicitly.

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?

There is an implied when-to-use: call this to obtain hub ids before using a hub-detail tool, and the 'only anonymous hub-discovery path' note hints at why this exists. However, there is no explicit when-not guidance and no named alternative tool, so the agent must infer the routing.

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

Deploy Server