Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm registry changes

npm_registry_changes_list
Read-onlyIdempotent

List 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

NameRequiredDescriptionDefault
limitNoChanges per page, 1 to 1000. Default: 100.
sinceNoStart 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`.
cursorNoCursor from `page.nextCursor` of the previous response. It only continues the same lookup and filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe 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_idNoEcho 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: results include deleted-document markers (tombstones) and paging is continued via the returned cursor. It omits rate limits and whether markers appear inline or as separate entries, so it stops short of a 5.

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?

Two tight sentences with the core purpose front-loaded and no wasted framing. The middle clause listing the three optional inputs largely duplicates the schema and is the one low-value fragment.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values, yet it only says 'Returns a list' and never characterizes a change record or how a deleted-document marker appears. Enough to call the tool, not enough to interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema text is unusually rich (mutual exclusion of `since`/`cursor`, default page size, cursor provenance). The description's mention of the same three optional inputs adds nothing new, but the structured fields already carry full semantics; per the baseline this is capped at 3 only when the description is silent and the schema is the sole source.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List npm registry changes') and adds two distinguishing traits: sequence-cursor paging and deleted-document markers. It does not differentiate from close siblings such as npm_registry_recent_list, so the agent still has to infer which change-feed to use.

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?

Gives one concrete usage rule ('use cursor when paginated'), reinforced by the schema note that `since` cannot be combined with `cursor`. It offers no when-to-use versus when-not guidance relative to the other recent/changes feeds, so selection is only implied.

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