Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm org or scope packages

npm_org_packages_list
Read-onlyIdempotent

List the packages an npm org or scope can publish, 25 per page. Use the cursor to page through results when the response is paginated.

Instructions

List the packages an npm org or scope can publish, 25 per page. 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_org_packages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. npm org or scope name, e.g. `babel`. Case-sensitive.
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.
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.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world behavior, so the description only needs to add operational detail — and it does, disclosing the fixed page size of 25 and the cursor-based continuation model. It does not cover rate limits or auth requirements, which keeps it from a 5.

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 sentences with the scope constraint and page size front-loaded, so an agent gets the essentials immediately. The parenthetical '(use cursor when paginated)' is slightly redundant phrasing but does not waste much space.

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 read-only listing tool with full schema coverage and no output schema, the description covers purpose, required input, result shape ('returns a list') and pagination, which is enough to call it correctly. Additional detail on ordering or what fields each package entry carries is not strictly necessary here.

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 all six parameters including `context`, `llm_model` and `conversation_id` are already documented in the schema. The description only restates that `name` is required and gestures at the cursor, adding little meaning beyond what the schema already provides.

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 gives a specific verb and resource — listing packages an npm org or scope can publish — which separates it from the user- and registry-scoped siblings without naming them. It stops short of explicitly naming the alternative tools an agent should consider, but the scope is unambiguous.

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?

Usage is only implied: the description says `name` is required and that the cursor should be used 'when paginated', which hints at pagination flow but never states when to pick this over npm_user_packages_list or npm_registry_packages_list. No exclusions or prerequisites are given.

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