Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Stack Overflow users

stack_overflow_users_batch_get
Read-onlyIdempotent

Retrieve up to 100 Stack Overflow users by ID in a single call to fetch profile data for multiple users at once.

Instructions

Get up to 100 Stack Overflow users in one call, by id. Requires ids.

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

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. User ids, comma-separated, 1 to 100, e.g. `22656,1144035`. Duplicates are dropped. `-1` is the Community user.
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.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and repeatability profile is covered structurally. The description adds only the batch ceiling, and says nothing about behavior the annotations cannot express: what happens when an id does not exist (omitted vs. error), whether results preserve the requested id order, or whether partial failures are tolerated. It does not contradict the annotations.

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?

Two short clauses, front-loaded with the action and its scale limit, with the required input called out last. No filler, no redundancy, and nothing an agent must read past to reach the operative constraint.

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 batch read with full annotation coverage and a fully documented schema, the essentials are covered, and no output schema exists so return values need not be explained. Still, the description omits the `site` dimension (the name says Stack Overflow, yet the schema allows askubuntu, math, ru.stackoverflow, etc.) and says nothing about missing-id handling, both of which matter more for a batch call than for a single fetch.

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 the schema already documents ids bounds, comma-separated examples, duplicate dropping and the `-1` Community user convention, plus site defaults and the analytics-only context/llm_model fields. The description only restates that `ids` is required, adding no syntax or constraint meaning beyond the schema, so 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?

States a specific verb and resource ("Get ... Stack Overflow users"), the batch size ceiling (up to 100), and the lookup key (by id). The plural/batch framing implicitly distinguishes it from the single-user sibling stack_overflow_user_get, though it never names an alternative outright.

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?

"in one call" plus "up to 100" signals this is the bulk path, and "Requires `ids`" states a prerequisite, so usage is inferable. But there is no explicit when-to-use-vs-when-not guidance and no mention of stack_overflow_user_get for single lookups or stack_overflow_users_search for name-based lookup, which is the main routing decision an agent faces here.

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