Crawlora MCP

itchio_jams_entries

Read-only

Read the full native public submissions document for one itch.io game jam and return the path, resolved entries JSON URL, fractional generated_on timestamp and every jam game entry with its submission id/url, created-at string, coolness, rating count, project game metadata and optional contributor credits and metadata. Pass the native relative /jam/slug/entries path from a public jam's Submissions tab or jam browse's submissions link; the current numeric jam resource is resolved from the page and callers never supply it. Source ordering is retained and the site applies search, platform, sort and pagination filters locally, so this tool accepts none of them; account state, rating queues/actions and comments are excluded.

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_jams_entries"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Required native relative destination from the previous jam response, e.g. /jam/gmtk-jam-2026/results for criteria discovery, /jam/gmtk-jam-2026/entries for submissions, /jam/godot-wild-jam-99 for the overview, or /jam/gmtk-jam-2026/rate/4794047 for submission metadata. Pass it unchanged; hidden/unpublished resources return 404 and unsupported destinations are rejected.

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.

AddedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses that source ordering is retained, that the site applies search/platform/sort/pagination locally so the tool accepts none of them, and that account state, rating queues/actions and comments are excluded. That is real behavioral context an agent could not infer from annotations. It does not discuss pagination limits or result-size behavior, which matters for a 'full document' read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The invocation and constraint sentences are front-loaded and useful, but the first sentence is a long enumeration of return fields that duplicates what the existing output schema already documents. Roughly half the text is spent restating the response shape rather than adding selection guidance.

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 single-parameter read tool with full schema coverage, an output schema and read-only annotations, the definition covers what is needed: where the path comes from, what is resolved internally, what filters are unsupported, and what is out of scope. The only shortfall is redundancy — return-value detail is explained despite the output schema, and no sibling is named for the filtered-results case.

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%, so the baseline is 3, but the description adds genuine meaning: the path must be the native relative entries destination, the numeric jam resource is derived from the page rather than supplied, and the path is passed unchanged. That clarifies the one parameter's provenance and constraints beyond the schema's own wording.

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: read the full native public submissions document for one itch.io game jam, and enumerates the returned entities (submission id/url, coolness, rating count, project metadata, credits). The scope is clearly narrower than a rankings/results fetch, but the description never names the sibling tools (itchio_jams_results, itchio_jams_submission) it must be distinguished from, leaving that differentiation to the schema's path examples.

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 invocation guidance: pass the native relative /jam/slug/entries path taken from a public jam's Submissions tab or the jam browse submissions link, and notes the numeric jam resource is resolved internally so callers never supply it. It also rules out search/platform/sort/pagination parameters and excludes account state, rating actions and comments. It stops short of naming which sibling to use instead when the agent actually wants filtered results.

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.