Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm recent package updates

npm_registry_recent_list
Read-onlyIdempotent

Lists npm package updates in reverse chronological order, at most 50 items, to help you track recent package changes.

Instructions

List recent npm package updates, newest first, at most 50 items. Returns a list.

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_recent_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description only needs to add beyond that. It does add two useful operational facts — newest-first ordering and a hard cap of 50 — but says nothing about pagination, cursors, or how to retrieve items beyond the first 50, which is the main behavioral unknown for a capped list.

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 short sentences with the scope constraint (newest first, max 50) front-loaded. "Returns a list" is largely redundant for a tool already named *_list, costing a little tightness but not readability.

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 must stand in for return-value expectations, and "Returns a list" plus the 50-item cap is thin — item shape and field contents are unspecified. For a simple read-only list tool this is adequate but not complete, especially given the absence of any pagination story.

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% and all three parameters (context, llm_model, conversation_id) are fully documented in the schema, so the baseline is 3. The description adds no parameter meaning at all, and notably never mentions that the tool accepts no filtering, paging, or count parameters — a fact an agent would only learn from opening the schema.

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 recent npm package updates") plus ordering, so the agent knows exactly what it returns. It falls short of a 5 because it never distinguishes itself from close siblings such as npm_registry_changes_list or npm_package_versions_list, leaving the agent to infer which 'recent list' is appropriate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative. The phrase "recent" implies a context, but the definition never says whether this is for discovering ecosystem activity versus tracking a specific package, which is the key routing decision against the listed siblings.

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