Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stack Overflow user

stack_overflow_user_get
Read-onlyIdempotent

Retrieve a Stack Overflow user's profile by member ID for reputation, badges, activity counts, location, website, and profile text.

Instructions

Get a Stack Overflow user's profile: reputation, badges, activity counts, location, website and profile text. Requires memberId.

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

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
memberIdYesRequired. User id on the chosen site, e.g. `22656`. `-1` is the Community user.
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.3/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's contribution is the enumeration of returned fields, valuable since there is no output schema, but it says nothing about failure behavior for invalid ids or cross-site id resolution.

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 sentence with the profile scope front-loaded before the field list and the required-parameter note. No redundant phrasing or filler.

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 simple single-resource getter with annotations covering safety and no output schema, the field enumeration makes it largely callable. The remaining gap is how the agent should obtain a valid `memberId` and whether batches are preferable, which the definition never addresses.

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%, including the `-1` Community-user convention and the `site` default, so the schema already carries parameter meaning. The description merely restates that `memberId` is required and adds no syntax or edge-case detail beyond the schema.

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 ('Get a Stack Overflow user's profile') and enumerates the returned data (reputation, badges, activity counts, location, website, profile text), which separates it from the sibling list tools like stack_overflow_user_answers_list. It does not explicitly name a sibling to route against, which keeps it below a 5.

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 'Requires `memberId`', which is a prerequisite rather than a when-to-use rule. There is no mention of when to prefer stack_overflow_users_search (to obtain an id) or stack_overflow_users_batch_get (for multiple users), so the agent must infer the routing.

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