Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm package versions

npm_package_versions_list
Read-onlyIdempotent

List 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

NameRequiredDescriptionDefault
nameYesRequired. 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 `-`.
limitNoVersions per page, 1 to 200. Default: 100.
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.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, so the bar is lower; the description still adds real value by declaring sort order and the exact data included (deprecation, provenance, integrity, sizes). It doesn't mention rate limits or result-size expectations beyond the cursor note.

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?

Three short sentences, front-loaded with the action and payload, then the requirement and pagination note. 'Requires `name`' mildly duplicates the schema's required list, but nothing is bloated.

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?

For a read-only paginated list with complete annotations and full schema coverage, the description covers ordering, contents, prerequisite, and cursor continuation. The absence of an output schema is partly offset by enumerating returned fields, though no example response shape is given.

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 description coverage is 100%, with name, limit, and cursor fully documented in the schema, so the schema carries the burden. The description only restates that `name` is required and that the cursor drives pagination, adding no format or edge-case detail beyond structured fields.

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?

The description gives a specific verb and resource ('List an npm package's versions') and adds the ordering ('newest first') plus the payload fields returned. It never names a sibling such as npm_package_version_get, so an agent must infer the boundary between listing versions and fetching a single version.

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?

It states the prerequisite ('Requires `name`') and hints at pagination continuation ('use cursor when paginated'), which is enough to call the tool. There is no explicit when-to-use/when-not or pointer to the single-version or provenance siblings that overlap with the fields this returns.

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