Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm downloads for several packages

npm_packages_downloads_batch_get
Read-onlyIdempotent

Get npm download counts for up to 128 package names in a single call, returning one result per requested name. Use it to compare package popularity or pull batch download stats by period or date range.

Instructions

Get npm downloads for up to 128 package names in one call, one result per requested name. Requires names. 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": {
      "names": "<names>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_packages_downloads_batch_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`.
namesYesRequired. Comma-separated package names, 1 to 128, with at most 20 scoped names because each one is looked up separately.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only output cardinality ("one result per requested name") and a return-shape hint; it omits real behavioral traits that live only in the schema, such as the 18-month range clamping and the conversation_id handshake that forbids parallel calls.

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 front-loaded sentences with the batch capability and cardinality stated first. "Returns a list" earns its place because no output schema exists, though "Requires `names`" duplicates the schema's required array.

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 8 parameters and no output schema, the definition is adequate but thin: it never mentions the mandatory analytics parameters (context, llm_model) or the conversation_id sequencing rule that materially affects how the tool is called. The range-clamping and scoped-name limits exist only in the schema, leaving the description under-informative for a tool of this complexity.

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 schema already documents every parameter including the 128-item cap and the 20-scoped-name sub-limit. The description restates `names` as required without adding syntax or constraint meaning beyond the schema, so the baseline of 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?

States a specific verb and resource ("Get npm downloads") plus the batch scope ("up to 128 package names in one call, one result per requested name"), which implicitly separates it from the single-package npm_package_downloads_get sibling. It stops short of naming the competing tools, so the differentiation is inferable rather than explicit.

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 phrase "in one call" implies this is the tool for multiple packages, but there is no explicit when-to-use/when-not-to-use statement or pointer to the singular alternatives. Nothing tells the agent whether to prefer this over N separate calls, nor how `period` versus `from`/`to` should be chosen.

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