Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Stack Overflow questions

stack_overflow_questions_batch_get
Read-onlyIdempotent

Retrieve up to 100 Stack Overflow questions by ID in one batch call, optionally including answers or comments.

Instructions

Get up to 100 Stack Overflow questions 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_questions_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Question ids, comma-separated, 1 to 100, e.g. `11227809,927358`. Duplicates are dropped.
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.
includeNoExtra parts to return with each question: `answers`, `comments`, or both, comma-separated. Default: neither. With either, a request takes at most 10 ids.
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.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the batch cap, which the schema's maxItems:100 already states, and says nothing about the 10-id limit when `include` is used or about the conversation_id/llm_model handshake requirements.

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 sentences, front-loaded with the operation and batch size, with no filler. The trailing "Requires `ids`" is largely redundant with the schema's required array, a minor waste.

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 six-parameter batch tool with no output schema, the description covers what the tool returns only implicitly and says nothing about the `include`-driven 10-id restriction or the analytics/conversation parameters. The rich schema compensates, leaving this minimally adequate rather than complete.

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 every parameter (ids, site, include, context, llm_model, conversation_id) is already documented in the schema. The description only restates that `ids` is required, adding no meaning beyond that, so the baseline of 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 questions) plus the batch shape and key ('by id', up to 100 per call). This implicitly distinguishes it from single-question and search siblings, though it never names an alternative explicitly.

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?

"by id. Requires `ids`" implies you must already hold the ids and should use a search/list sibling otherwise, but that routing is left to inference. No explicit when-to-use, when-not-to-use, or named alternatives 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