Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm package dependents

npm_package_dependents_list
Read-onlyIdempotent

Find npm packages that depend on a specified package and page through results 36 at a time using cursor-based pagination.

Instructions

List packages that depend on an npm package, 36 per page; a page past the served list is empty. Requires name. 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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_package_dependents_list"
  }
}

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 `-`.
pageNo1-based page number. Each page carries 36 rows and the list stops at page 11; a page past it is an empty page. Default: 1.
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.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add genuine context beyond that: fixed 36-row pages, empty page past the served list, and cursor-based continuation. It stops short of describing what a dependent row contains.

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, front-loaded with the resource and page size. 'Requires `name`' and 'Returns a list' are near-redundant with the schema and required fields, but the waste is minor.

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?

For a read-only list tool with no output schema, the description covers purpose, page size and pagination but never says what fields a dependent entry carries. That leaves an agent unable to anticipate the response shape, though the annotations and full schema coverage compensate partly.

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 coverage is 100%, so every parameter is already documented, including the page cap and cursor semantics. The description only restates that `name` is required and that cursor applies when paginated, adding no meaning beyond the schema — baseline 3.

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: lists packages that depend on an npm package. That is clearly distinct from siblings like npm_package_versions_list or npm_package_downloads_get, though the description never names or explicitly contrasts those alternatives.

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?

The only guidance is mechanical ('Requires `name`', 'use cursor when paginated'). There is no statement of when to prefer this tool over related npm lookup tools, no prerequisites, and no exclusions.

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