Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_jams_entries

Retrieves full published JSON of itch.io game-jam submissions from a jam's native entries path, preserving entry order, project IDs, credits and zero counts for local filtering and sorting.

Instructions

Read itch.io game-jam submissions. Resolves the current native submissions JSON URL from the public jam page and returns its full published document. Preserves source ordering, entry and project ID namespaces, generated_on, zero counts, contributor credits and optional project metadata. The upstream UI filters, sorts and paginates this document locally; this endpoint accepts no server-side filter, sort or page parameters. Account, rating and custom private submission data 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

NameRequiredDescriptionDefault
pathYesNative relative /jam/slug/entries path linked by a public jam

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/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 behavioral burden and does so well: it discloses the two-step resolution (resolve URL from public jam page, then return the full published document), what is preserved (ordering, ID namespaces, generated_on, zero counts, credits), and what is excluded (account, rating, private data). It falls short of stating auth/exposure guarantees explicitly beyond 'public jam page'.

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?

Content is front-loaded: purpose first, then resolution behavior, then what is preserved, then what is excluded. Dense but each sentence adds distinct information; no filler or restatement of the name.

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 and a single parameter, so the description must characterize the return value — it does so via the preservation/exclusion lists and the promise of the 'full published document'. A brief note on the response envelope shape would close the remaining gap, but an agent can invoke this correctly as written.

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?

Only one parameter with 100% schema description coverage, so baseline is 3. The description adds that the path points at a document whose URL is dynamically resolved as 'current', implying the caller need not construct the full URL — but it adds no format or validation detail beyond the schema's '/jam/slug/entries' hint.

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 itch.io game-jam submissions', plus the resolution mechanism (native submissions JSON URL from the public jam page). An agent knows exactly what this fetches, though it does not name a sibling (e.g. itchio_jams_results) to contrast with.

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?

Conveys an implied when-to-use boundary by stating that filtering, sorting and pagination are done client-side and this endpoint accepts no such parameters — useful for ruling out server-side queries. However it never names an alternative tool or states a positive condition for choosing this over itchio_jams_results, so guidance is implied rather than explicit.

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