List npm package versions
npm_package_versions_listList an npm package's versions newest first with publication time, deprecation, provenance, integrity and sizes, so you can audit release history and pick the right version.
Instructions
List an npm package's versions newest first, with publication time, deprecation, provenance, integrity and sizes. Requires name. Returns a list (use cursor when paginated).
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": {
"name": "<name>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "npm_package_versions_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Required. npm package name, e.g. `express`, `lodash.merge`, `@types/node` or `--file--1`. Names are case-sensitive (`Express` is a different package) and keep legacy punctuation such as a leading `-`. | |
| limit | No | Versions per page, 1 to 200. Default: 100. | |
| cursor | No | Cursor from `page.nextCursor` of the previous response. It only continues the same lookup and filters. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |