Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Stack Overflow users

stack_overflow_users_search
Read-onlyIdempotent

Search Stack Overflow users by name, reputation, or join date to find contributors matching specific criteria across Stack Exchange sites.

Instructions

Search Stack Overflow users by name, reputation or when they joined. Optional inputs: site, name, sort, order, joinedAfter and 6 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_users_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the display name to look for (not case sensitive).
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
sortNoOrder: `reputation` (default), `creation` (the only one that pages without a ceiling), `name` or `modified`. Ties can repeat or skip rows.
limitNoUp to this many rows per page, 1 to 100. Default: 30. A page can hold fewer than `limit` rows where rows share a creation second or a block of 100 rows ends. Follow `page.nextCursor` until `hasMore` is false.
orderNoDirection of the sort: `desc` (default) or `asc`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`about` adds each user's profile text. Default: none.
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.
joinedAfterNoOnly users who joined at or after this time, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC.
joinedBeforeNoOnly users who joined before this time, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC.
reputationMaxNoOnly users with at most this reputation. Needs `sort` of `reputation`.
reputationMinNoOnly users with at least this reputation. Needs `sort` of `reputation`.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that the result is a list and that a cursor drives pagination, but says nothing about result ordering guarantees, empty-result behavior, or the conversation_id handshake that the schema introduces.

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 front-loaded sentences with the purpose first and pagination note second. The 'and 6 more' phrasing is imprecise but keeps it short rather than bloating the definition.

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 14-parameter, non-destructive search with no output schema, the description covers the return shape only minimally ('Returns a list'). It omits any mention of the required context/llm_model/conversation_id plumbing that makes this call non-trivial, though the schema does document each fully.

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 the schema carries the full parameter burden with detailed per-field descriptions. The description only enumerates a few names and trails off with 'and 6 more', which adds no meaning and slightly obscures the full parameter set; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Stack Overflow users') plus the filterable dimensions (name, reputation, join date), which distinguishes it from the single-record sibling stack_overflow_user_get and the batch sibling.

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 a parenthetical about using the cursor when paginated. It never says when to prefer this over stack_overflow_user_get, batch_get, or the site-specific user list tools, leaving routing to inference from names.

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