List npm registry changes
npm_registry_changes_listList npm registry changes from a sequence cursor, including deleted-document markers, with pagination via cursor to track package and registry updates over time.
Instructions
List npm registry changes from a sequence cursor, with deleted-document markers. Optional inputs: since, limit and cursor. 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": {
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "npm_registry_changes_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Changes per page, 1 to 1000. Default: 100. | |
| since | No | Start after this sequence. Omit it or use `0` for the oldest changes. No call returns the current sequence: for recent changes pass one such as `141000000`, then your stored `lastSeq`. Not with `cursor`. | |
| 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. |