Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm downloads for every version

npm_package_version_downloads_get
Read-onlyIdempotent

Retrieve last week's npm download counts for every version of a specified package to compare version adoption and track usage trends.

Instructions

Get last week's npm downloads for every version of a package. Requires name.

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

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 `-`.
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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and liveness profile is covered. The description adds the meaningful non-annotation detail that the measurement window is 'last week' and reinforces the `name` requirement. It does not describe the response shape (a version-to-count mapping), which is a gap given there is no output schema.

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 time window and scope front-loaded, so the key facts arrive first. The second sentence ('Requires `name`') is largely redundant with the schema's required list, slightly reducing efficiency.

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?

This is a simple read-only lookup with fully documented parameters and thorough annotations, so little narrative is needed. The one substantive omission is what the result looks like (per-version download counts), which matters because no output schema exists.

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%, so all four parameters (including `name` with its case-sensitivity and scoped-package examples) are already documented in the schema. The description adds nothing about parameter semantics beyond repeating that `name` is required, so the baseline 3 applies.

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 names a specific verb and resource ('Get last week's npm downloads') and scopes it to 'every version of a package', which distinguishes it from a package-total downloads tool. It stops short of naming the sibling (npm_package_downloads_get) explicitly, so the differentiation is inferred rather than stated.

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 guidance: no mention of when to prefer this per-version breakdown over the package-level or batch download tools, and no exclusions. 'Requires `name`' is a restatement of the schema's required field, not usage guidance, leaving selection entirely to inference from the phrase 'every version'.

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