Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_project

Retrieve public itch.io project details from a creator.itch.io URL, including title, summary, description, cover image, and More information links. Excludes downloads and account data.

Instructions

Get itch.io public project details. Returns source project ID, title, summary, project description, cover URL and every available More information row/link. Uses public HTTPS creator.itch.io project pages only; source schema metadata provides title fallback. Download instructions, community text, credentials and account/purchase/download requests 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": {
      "url": "<url>"
    },
    "name": "itchio_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS creator.itch.io/project URL without query or fragment

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 provided, the description carries the behavioral burden and does so fairly well: it lists return fields, restricts the source to public project pages, describes a title fallback, and excludes downloads, community text, credentials, and account/purchase/download requests. It does not discuss error behavior, rate limits, or authentication beyond excluding credentials.

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?

The description is front-loaded with the core purpose and return fields, then adds scope and exclusions efficiently. It is slightly repetitive about the public creator.itch.io URL restriction but remains compact and readable.

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 simple public project-fetch tool with no output schema, the description explains what is returned and what is out of scope. It is nearly complete, though it could mention error or pagination behavior if applicable.

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 description coverage is 100%, so the single URL parameter is already fully documented in the schema. The description reinforces that only public HTTPS creator.itch.io project pages are accepted, but adds no new syntax or formatting details beyond what the schema provides.

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?

The description states a specific verb and resource: 'Get itch.io public project details.' It clearly scopes the tool to a single project page and lists the returned fields, though it does not explicitly contrast itself with sibling browse/catalog tools.

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 the required project URL and the note that only public HTTPS creator.itch.io project pages are used. The exclusions clarify scope, but the description does not explicitly say when to use this tool versus alternatives such as itchio_browse or itchio_catalog.

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