Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm package downloads

npm_package_downloads_get
Read-onlyIdempotent

Retrieve npm package download counts for a selected period, custom date range, or the entire registry, with totals or daily granularity.

Instructions

Get npm downloads for a package over a period or a day range, or the whole registry's total. Optional inputs: name, period, from, to and granularity.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the range, `YYYY-MM-DD`. Must be on or after `from`; a `to` before 2015-01-10 is refused. A range spans up to 18 months; a longer range keeps its newest 18 months and sets `clamped`.
fromNoFirst day of the range, `YYYY-MM-DD`. Download data starts on 2015-01-10; a `from` after today is refused. A range spans up to 18 months; a longer range keeps its newest 18 months and sets `clamped`.
nameNoPackage name. Omit it for the whole registry's download total.
periodNoWindow: `last-day`, `last-week`, `last-month` or `last-year`. Default: `last-week` unless `from`/`to` are given.
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.
granularityNo`total` for one number, `daily` for one row per day. Default: `total`.
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.5/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive open-world fetch, so the safety profile is covered. The description adds only the notion of aggregate registry totals as a distinct behavior; it says nothing about refusal conditions, clamping of long ranges, or rate limits, all of which the schema handles instead.

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 sentences, front-loaded with the capability and its modes. The trailing "Optional inputs: ..." clause largely restates what the schema already declares, costing a small amount of space without adding information.

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?

With an 8-parameter schema fully documented, annotations covering safety, and no output schema to explain, the description needs only to convey the tool's modes and scope — which it does. The remaining gaps (granularity's effect on shape, refusals) are already handled by the rich schema.

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 the baseline is 3. The description merely names `name`, `period`, `from`, `to`, and `granularity` without adding any meaning beyond what the schema already states, and it omits `context`/`llm_model`/`conversation_id` entirely.

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 opens with a specific verb and resource ("Get npm downloads for a package") and enumerates the three modes it covers: period, explicit day range, and whole-registry total. It does not, however, differentiate itself from the similarly-named siblings that surface in the catalog (version-level downloads, batch downloads), so an agent must still infer that distinction.

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?

The three modes imply when to supply `name`, `period`, or `from`/`to`, but the guidance is left implicit rather than stated. There is no explicit when-not or routing toward an alternative tool, and the key scoping rule (omit `name` for registry totals) lives only in the schema.

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