Maven Central

List Versions

list_versions

Read-onlyIdempotent

List all published versions of a Maven artifact identified by groupId and artifactId, with release timestamps, using the Maven Central Solr GAV core.

Input Schema

TableJSON Schema

Name	Required	Description
`rows`	No	1-200 (default 200)
`group_id`	Yes
`artifact_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of versions returned
`group_id`	Yes	groupId queried
`versions`	Yes	Published versions with release dates
`artifact_id`	Yes	artifactId queried

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "artifact_id": "spring-boot-starter-web",
+    "group_id": "org.springframework.boot"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artifact_id": {
+      "description": "artifactId queried",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of versions returned",
+      "type": "number"
+    },
+    "group_id": {
+      "description": "groupId queried",
+      "type": "string"
+    },
+    "versions": {
+      "description": "Published versions with release dates",
+      "items": {
+        "properties": {
+          "released": {
+            "description": "ISO 8601 release timestamp or null if unavailable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "version": {
+            "description": "Version string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "version",
+          "released"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "group_id",
+    "artifact_id",
+    "count",
+    "versions"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, destructiveHint. The description adds minimal extra behavioral context (uses Maven Central Solr GAV core). It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that efficiently conveys the tool's purpose. No unnecessary words.

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?

Given the tool's simplicity and the presence of rich annotations and an output schema, the description is mostly complete. However, it does not explicitly state that the output is a list of versions, which is minor.

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 33% (only 'rows' has description). The description mentions groupId and artifactId but adds no additional syntax or format details. It partially compensates by clarifying their role, but does not fully compensate for the low schema coverage.

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 clearly states the verb 'list', the specific resource 'published versions of a Maven artifact', and the identifying parameters. It distinguishes from siblings like 'latest_version' by implying a listing of all versions.

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?

The description implies usage for listing all versions of a Maven artifact, but does not explicitly state when to use this over sibling tools like 'latest_version' or 'search'. It lacks 'use this when' guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Maven Central 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.