Crawlora MCP

itchio_browse

Read-only

Browse one native itch.io catalog context through a relative path returned by itchio_browse_options or the tag picker, and return the native classification, page, item count and every visible project card (id, title, canonical URL, description, creator and creator URL, cover image, displayed price and genre). Pass path unchanged (for example /games/top-rated or /tools/newest) and a one-based page defaulting to 1; arbitrary hosts, query strings, fragments, traversal and trailing slashes are rejected, and pagination is passed to the source without an invented page limit or cursor. All nine classifications are supported and a genuine empty page returns an empty items list.

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": {
      "path": "<path>"
    },
    "name": "itchio_browse"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Optional one-based native page, 1 to 100000. Omit it for page 1; pagination is passed to the source without an invented cursor.
`path`	Yes	Required relative native catalog path returned by itchio_browse_options or the tag picker, e.g. /games/top-rated or /tools/newest. Pass it unchanged: arbitrary hosts, query strings, fragments, traversal and trailing slashes are rejected. All nine classifications are supported.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedInput schema / properties / page / description

Previous value: -"Optional one-based native page. Omit it for page 1; pagination is passed to the source without an invented page limit or cursor."New value: +"Optional one-based native page, 1 to 100000. Omit it for page 1; pagination is passed to the source without an invented cursor."

AddedNov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses input rejection rules (arbitrary hosts, query strings, fragments, traversal, trailing slashes), that pagination is forwarded without an invented limit or cursor, that all nine classifications are supported, and that an empty page yields an empty items list.

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 usage, then constraints, which is the right order. It is a long chain of clauses with some repetition of schema text (path rules, page default), but each clause carries usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with annotations and a full output schema, nothing material is missing: input provenance, validation behavior, pagination semantics, and empty-result handling are all covered.

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 both parameters are already documented with the same examples, the one-based default, and the 1–100000 bound. The description largely restates the schema rather than adding new syntax or format meaning.

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 and resource ('Browse one native itch.io catalog context') plus what is returned (classification, page, item count, project cards). It clearly distinguishes itself from itchio_browse_options, which produces the paths this tool consumes.

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?

Explicitly tells the agent where the required input comes from (a relative path returned by itchio_browse_options or the tag picker) and that the path must be passed unchanged. It stops short of naming when-not to use it, but the prerequisite routing is clear enough to select correctly.

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

All Crawlora MCP tools Inspect

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

Need Help?