Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

roblox_search

Search Roblox experiences by keyword to get universe IDs, player counts, votes, maturity, and URLs. Use page tokens for pagination; no account or inventory data.

Instructions

Search Roblox experiences. Searches Roblox experiences for q (1 to 256 characters). Each result has its universe and place ids, name, creator, genre, player_count, up and down votes, maturity and URL. Pass next_page back unchanged as page_token for the next page. No account, friend, purchase or inventory data is included.

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": {
      "q": "<q>"
    },
    "name": "roblox_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Experience search query
`page_token`	No	Opaque page token returned by a previous search

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A3.8/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 disclose meaningful behavior: the exact fields returned (universe/place ids, creator, genre, player_count, votes, maturity, URL), pagination mechanics, and the scope limits on data types. It omits auth/permission requirements and rate limits, so not 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?

Front-loaded and efficient, with each sentence adding facts about results, pagination, or scope. The opening two clauses ('Search Roblox experiences. Searches Roblox experiences for `q`...') are mildly redundant, so not a 5.

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, and the description compensates by enumerating the returned fields and explaining pagination, plus the query constraint. For a 2-parameter search tool this is nearly complete; only auth/permission context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), and the description adds real value beyond it: the `q` length constraint (1-256 chars) and the round-trip instruction to pass `next_page` back unchanged as `page_token`. These are non-obvious operational details absent from the schema.

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?

States a specific verb and resource ('Search Roblox experiences') and describes the result shape, so the agent knows it is a discovery/search tool rather than a detail lookup like roblox_game. It does not explicitly name sibling tools to differentiate, keeping it just below a 5.

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 implied by 'Search Roblox experiences', but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as roblox_game or roblox_rankings. The 'No account, friend, purchase or inventory data is included' line gives a useful scope boundary but is not routing guidance.

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

Deploy Server