Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_collection

Read a public Modrinth collection’s metadata and complete native project-ID list, preserving order, visibility, and timestamps while excluding the owner’s account identifier.

Instructions

Read a public Modrinth collection. Reads public collection metadata and its complete native project-ID list. Retains native list order, visibility, timestamps and nullable fields while excluding the owner's account identifier. Does not fetch project details or private collections.

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": {
      "id": "<id>"
    },
    "name": "modrinth_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBase62 collection ID from a public collection URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and delivers real behavioral detail: native list order is preserved, visibility and timestamps are retained, nullable fields are kept, and the owner's account identifier is deliberately stripped. Gaps remain on auth requirements and pagination/result size, which matter for a very large collection.

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 core action, then scoping, then exclusions in a compact four-sentence block. The opening pair ('Read a public Modrinth collection. Reads public collection metadata...') is slightly redundant, but nothing else is wasted.

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 exists, so the description shoulders the return-value explanation and does so by describing retained ordering, visibility, timestamps, nullable fields, and the excluded owner identifier. For a one-parameter read tool this is nearly sufficient; only auth expectations and behavior on oversized collections are unaddressed.

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 coverage is 100% and the single parameter already documents 'Base62 collection ID from a public collection URL'. The description only reiterates that the collection must be public, adding no format, validation, or error semantics beyond the schema, so the baseline 3 applies.

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 ('Read a public Modrinth collection') and immediately narrows the payload to metadata plus the native project-ID list. The singular/plural contrast with the sibling 'modrinth_collections' is reinforced by the scoping clauses, so an agent can distinguish the two without opening a 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 closing sentence gives explicit exclusions ('Does not fetch project details or private collections'), which tells the agent when this tool will not serve its need. It stops short of naming the alternative to use for project details or private collections, so it lands below a full when/when-not/alternatives statement.

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