Crawlora MCP

modrinth_collections

Read-only

Resolve a JSON array of public Modrinth collection IDs in one native bulk read and return the same public collection records as modrinth_collection, including each complete project-ID list, in native result order with source omissions and nulls preserved. Send exactly one ids array parameter; an empty array is valid. Duplicate IDs do not create local copies and missing IDs do not create placeholders; owner account identifiers and private/rejected data are excluded, and malformed input is rejected.

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": {
      "ids": "<ids>"
    },
    "name": "modrinth_collections"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Required JSON-encoded array of base62 collection IDs, for example ["20osG2HL","2I9Pp72E"]. An empty array is valid. This is one native bulk read: duplicates do not create local copies, missing IDs do not create placeholders, and native result order is preserved.

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

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses native result ordering, preservation of source omissions and nulls, that duplicates create no local copies and missing IDs no placeholders, that owner account identifiers and private/rejected data are excluded, and that malformed input is rejected — a full behavioral contract for a bulk read.

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 the operation and the bulk-read framing, then the parameter constraint, then the edge-case guarantees; every clause carries meaning. It is dense and somewhat repetitive with the schema's ids description, which keeps it from a 5.

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?

With an output schema present, return values need no explanation, yet it still notes the complete project-ID list is included. For a single-parameter bulk read, nothing an agent needs to invoke it correctly is missing.

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% and the schema already documents the JSON-encoded base62 array, empty-array validity, ordering, and duplicate/missing semantics. The description reinforces the 'exactly one parameter' constraint but adds little format detail beyond the schema, so it is a modest step above baseline.

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 ('Resolve a JSON array of public Modrinth collection IDs') and frames it as a bulk counterpart to the single-record tool modrinth_collection, so an agent can distinguish the two without opening either schema.

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?

The bulk-vs-single relationship with modrinth_collection is clear, and it explicitly says 'Send exactly one ids array parameter' and that an empty array is valid. It stops short of an explicit 'use modrinth_collection when you have a single ID' exclusion, leaving that routing to inference.

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.