pkg-peep

get_npm_downloads

Retrieve NPM package download statistics for any package, with options for predefined periods or custom date ranges.

Instructions

Get NPM package download statistics

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": {
      "package": "<package>"
    },
    "name": "get_npm_downloads"
  }
}

Input Schema

Name	Required	Description
`period`	No	Predefined time period for download stats
`endDate`	No	End date for custom range (YYYY-MM-DD format)
`package`	Yes	NPM package name
`startDate`	No	Start date for custom range (YYYY-MM-DD format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden for behavioral disclosure. It states the basic function but omits critical details such as how period interacts with startDate/endDate, whether the period and custom range are mutually exclusive, possible rate limits, or the structure of the returned statistics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the key verb and resource, and contains no redundant or filler information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (period enum, date range parameters, no output schema, no annotations), the description is far too minimal. It fails to explain the relationship between period and startDate/endDate, what constitutes 'download statistics' (e.g., counts, points in time), or any usage constraints, leaving significant ambiguity for the agent.

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% — all four parameters have clear descriptions in the input schema. The description adds no extra semantic value beyond what is already documented, so the baseline score of 3 is appropriate.

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 clearly states the tool retrieves NPM package download statistics using a specific verb ('Get') and resource ('download statistics'). However, it does not explicitly differentiate from the sibling tool get_npm_package_info, only implying a focus on downloads rather than package metadata.

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?

No guidance is provided on when to use this tool versus the sibling get_npm_package_info. There are no exclusions, prerequisites, or alternative tool mentions, leaving the agent without contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server