Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm user

npm_user_get
Read-onlyIdempotent

Fetch an npm user's profile details, including display name, GitHub handle, account dates, and package count, by username to verify identity or assess package activity.

Instructions

Get an npm user's profile: display name, GitHub handle, dates and package count. Requires username.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description earns credit by disclosing the shape of the return payload in the absence of any output schema, telling the agent it gets profile fields rather than a package list. It still says nothing about missing-user behavior or rate limits.

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, front-loaded sentences with the return shape leading and the prerequisite trailing. Nothing is wasted, though the closing 'Requires `username`' duplicates what the schema's required list and the username property description already state.

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 small, single-resource read tool with rich annotations and full schema coverage, the description covers purpose, returned fields and the key prerequisite. Only error and empty-result behavior are left unaddressed, which is a minor gap given there is no output schema to carry that information.

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 four parameters, including the unusual context, llm_model and conversation_id fields, are already documented in the schema. The description only repeats the username requirement and case sensitivity, adding no meaning beyond the structured data; baseline 3 applies.

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 pairs a specific verb and resource, 'Get an npm user's profile', with the exact fields returned (display name, GitHub handle, dates, package count), which lets an agent separate it from sibling list tools such as npm_user_packages_list. It stops short of naming any alternative explicitly, so the differentiation is inferred from the field list rather than stated.

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?

The only guidance is the stated prerequisite 'Requires `username`', which is really a restatement of the schema's required field. There is no instruction on when to reach for this tool versus profile-list or org siblings, nor any exclusion, so usage is only implied.

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