Crawlora MCP

modrinth_organization_projects

Read-only

List every anonymously visible project published by one public Modrinth organization and return the complete array in native order: project IDs/slugs, names, summaries, descriptions, types/games, compatibility and category lists, license, downloads/followers, timestamps, icon/gallery/link metadata and reviewed public Minecraft server metadata. Pass the organization ID or slug; the organization identity is validated first so a slug is never mistaken for an ID, and a valid organization may return an empty array. Project-type tabs and sorting on the website are local display state, so there is no project-type filter, synthetic pagination, aggregation or local sorting; account/team identifiers and moderation workflow 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": {
      "id": "<id>"
    },
    "name": "modrinth_organization_projects"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required native organization ID or slug from a public organization URL or from project/search metadata, for example tREwurHE or ModLabs. Slugs may contain letters, digits, dots, underscores and hyphens; the source spelling 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.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial behavior beyond them: identity validation ordering so a slug is never mistaken for an ID, the possibility of a valid empty array, and native (unsorted, unpaginated) ordering of the returned array. Those are exactly the operational facts an agent needs and none of them are in the structured fields.

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 operative constraints are front-loaded well, but the middle stretches into a long enumeration of returned fields (IDs/slugs, names, summaries, descriptions, compatibility, license, downloads, gallery, server metadata) that duplicates what the output schema already declares. That list adds bulk without adding selection-relevant meaning.

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 one fully documented required parameter, an output schema present, and annotations covering safety, the definition supplies everything still missing: ordering guarantees, empty-result behavior, and identifier validation. Nothing needed to call it correctly is absent.

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, and the description earns an extra point by explaining that the identifier is validated as organization identity before use and that slugs are never reinterpreted as IDs. It does not add format examples beyond the schema, so it is not a full 5.

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?

The description opens with a specific verb and resource: 'List every anonymously visible project published by one public Modrinth organization.' The scope qualifiers ('anonymously visible', 'one public organization') distinguish it from the broader project/search siblings like modrinth_projects and modrinth_search.

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?

It clearly states the calling precondition ('Pass the organization ID or slug') and explicitly lists what the tool does not do (no project-type filter, no synthetic pagination, no aggregation, no local sorting), which tells an agent not to reach for this tool expecting filtered or paged results. It does not name a sibling to use instead when filtering or pagination is needed, so it stops short of full alternative routing.

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.