Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_browse

Browse itch.io projects by native filter path, follow browse or tag paths, and retrieve ordered project cards with item counts across classifications, filters, sorts, and one-based pages.

Instructions

Browse itch.io projects by native filter path. Follow paths from browse options or tag discovery. Supports all nine classifications and native filter/sort combinations with one-based pages. Returns the source order, project cards and native item count; an explicit empty page returns an empty array.

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

NameRequiredDescriptionDefault
pageNoNative one-based page
pathYesRelative native catalog path, such as /games/top-rated/tag-horror

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/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, and it does disclose return shape (source order, project cards, native item count) and the empty-page edge case. It says nothing about rate limits, authentication, error behavior on malformed paths, or whether results are cached, so the safety profile remains incomplete.

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?

Four short sentences, each carrying distinct information — mechanism, sourcing of the path, capabilities, return contract — with the core purpose front-loaded. Slightly dense but no filler.

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

Completeness3/5

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

Adequate for a two-parameter read tool: the sourcing of `path`, classification coverage, and return/empty-page behavior are all covered, and no output schema exists so the description must explain returns, which it does briefly. It stops short of describing card fields or how item count relates to pagination.

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 already 100%, so a baseline of 3 applies, but the description adds real meaning: it explains how to obtain a valid `path` value (from browse options or tag discovery) and confirms page numbering is one-based. That workflow context is not in the schema itself.

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 ("Browse itch.io projects") plus the mechanism ("by native filter path"), which distinguishes it from catalog/tag/jam siblings. It does not explicitly name an alternative tool, but the mechanism is specific enough to separate it from listing tools.

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?

Gives concrete when-to-use guidance: obtain a path from browse options or tag discovery and then call this tool with it. No explicit exclusions or when-not guidance is provided, which is the only gap.

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

Deploy Server

Other Tools