Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search npm packages

npm_packages_search
Read-onlyIdempotent

Search npm registry packages by keywords and qualifiers, ranked by npm search score. Filter by author, maintainer, or scope and paginate results to find packages for your project.

Instructions

Search the npm registry by words and qualifiers, ranked by npm's search score; a page past the results is empty. Requires query. Returns a list (use cursor when paginated).

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_packages_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. The registry accepts a starting offset only up to 5000, so a page past the reachable results is an empty page. Default: 1.
sortNoRanking: `optimal` (npm's blend), or a single component. Default: `optimal`.
limitNoResults per page, 1 to 250. Default: 20.
queryYesRequired. Search text, 2 to 64 characters. A single emoji counts as two characters. The registry's qualifiers work: `author:isaacs`, `maintainer:`, `keywords:a,b`, `not:deprecated`, `@scope`.
cursorNoCursor from `page.nextCursor` of the previous response. It only continues the same lookup and filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
qualityNoQuality weight, 0 to 1.
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.
popularityNoPopularity weight, 0 to 1.
maintenanceNoMaintenance weight, 0 to 1.
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

A4.4/5.0
Behavior4/5

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

It discloses a critical operational constraint not explicitly detailed in the structured data: 'a page past the results is empty.' This prevents the agent from wasting calls beyond the reachable result set.

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 definition is extremely concise, utilizing two clear sentences to cover the core function, ranking mechanism, and pagination limits efficiently. There is no unnecessary language.

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?

Given the complexity of the input schema (11 parameters including weights and context), the description is suitably high-level. It covers the two most important functional constraints: the ranking logic and the end-of-results indicator.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is 100%, the baseline is already high. The description adds value by reinforcing the requirement for 'query' and clarifying that the ranking is based on 'npm's search score,' providing vital semantic context beyond the data types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action (Search), the resource (npm registry), and the methodology (by words and qualifiers, ranked by npm's search score). It is perfectly clear what the tool achieves.

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

Usage Guidelines4/5

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

It provides strong guidance on limitations, specifically that the results are ranked by npm's search score and that one must use a cursor for paginated results. This distinguishes it from a simple list tool.

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