Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm user packages

npm_user_packages_list
Read-onlyIdempotent

List the npm packages a specified user can publish, 25 per page, using their username; follow the returned cursor to page through results.

Instructions

List the packages an npm user can publish, 25 per page. Requires username. 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": {
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_user_packages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. 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.
usernameYesRequired. npm username, e.g. `sindresorhus`. Case-sensitive.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds useful non-structured detail: a fixed page size of 25 and the guidance to use a cursor when paginated, which the annotations don't convey.

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?

A single compact sentence cluster with the key constraint (username required) and pagination behavior front-loaded. No filler or redundant wording.

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?

For a paginated list tool with full schema coverage and annotations, the definition covers the essentials: required parameter, page size, and cursor usage. It doesn't describe the shape of returned package entries, but no output schema exists and the tool is simple enough that this is a minor gap.

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 all six parameters are already documented in the schema. The description restates that `username` is required and briefly mentions cursor continuation but adds no format or semantics beyond the schema, making 3 the appropriate baseline.

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 ('List the packages an npm user can publish') with a clear scope that distinguishes a user's publishable packages from org or registry-wide listings. It doesn't explicitly name the sibling tools, so it stays at 4 rather than 5.

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?

Mentions the required `username` and points to the cursor for pagination, which gives implied usage context. It does not say when to prefer this over npm_org_packages_list or npm_registry_packages_list, leaving the selection to inference.

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