Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stack Overflow question

stack_overflow_question_get
Read-onlyIdempotent

Fetch a Stack Overflow question by ID to retrieve its text, tags, votes, closed or locked state, and optionally answers and comments for research or debugging.

Instructions

Get a Stack Overflow question with its text, tags, votes, closed or locked state and, if asked, its answers and comments. Requires questionId.

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": {
      "questionId": "<questionId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_question_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.
includeNoExtra parts to return with the question: `answers`, `comments` (the question's comments, and each answer's when `answers` is also asked for), or both, comma-separated. Default: neither.
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.
questionIdYesRequired. Question id on the chosen site, e.g. `11227809`.
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 profile is fully covered. The description contributes the shape of the response and the conditional inclusion of answers/comments, but says nothing about auth needs, rate limits, or behavior when the question is deleted or the id is invalid.

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?

A single front-loaded sentence lists the returned data before the conditional extras, which is the right ordering. The trailing "Requires `questionId`" duplicates the schema's required array and does not earn its place.

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?

With no output schema, the description usefully enumerates the returned fields, and the rich schema covers all six parameters. The only real gap is that nothing describes error or not-found behavior for an invalid questionId, which matters for an open-world 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 site, include, context, llm_model and conversation_id are already well documented in the schema. The description only restates the questionId requirement and gestures at the optional `include` behavior, adding essentially nothing beyond 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 names a specific verb and resource ("Get a Stack Overflow question") and enumerates the payload (text, tags, votes, closed/locked state, optional answers and comments), so an agent knows exactly what comes back. It does not explicitly contrast itself with stack_overflow_questions_batch_get or stack_overflow_questions_list, leaving that differentiation to the singular questionId argument.

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?

Usage is implied rather than stated: the singular `questionId` requirement signals a single-question lookup, and "if asked" hints that answers/comments are opt-in. There is no explicit when-to-use/when-not or named alternative for fetching multiple questions, so the agent must infer the boundary from siblings on its own.

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