Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow questions

stack_overflow_questions_list
Read-onlyIdempotent

List Stack Overflow questions by tag, date, votes, activity, or unanswered status, and find related or linked questions for research and debugging.

Instructions

List Stack Overflow questions by tag, time range, votes or activity, or the questions related to or linking to one. Optional inputs: site, sort, order, tagged, unanswered and 7 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_questions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
sortNoOrder: `creation` (default, no ceiling), `activity`, `votes`, `hot`, `week` or `month`. Ties can repeat or skip rows. `hot`, `week` and `month` take no date range, `unanswered`, `relatedTo` or `linkedTo`.
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.
taggedNoOnly questions that carry all of these tags, comma-separated, up to 5, e.g. `python,pandas`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`body` adds the question text (HTML and Markdown) to each row. Default: none.
linkedToNoQuestions that link to this question id.
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.
relatedToNoQuestions shown as related to this question id.
unansweredNo`true` for questions with no answers. Cannot be combined with `relatedTo` or `linkedTo`.
createdAfterNoOnly questions asked 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.
createdBeforeNoOnly questions asked 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.
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.4/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 only added behavioral fact is "Returns a list (use cursor when paginated)," which is thin and largely duplicated by the `cursor` and `limit` schema text.

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 sentences, purpose front-loaded with the pagination note at the end. The middle clause "Optional inputs: `site`, `sort`, `order`, `tagged`, `unanswered` and 7 more" is filler that restates the schema and could be dropped without loss.

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 15-parameter tool with no output schema, the description covers the basic return shape and cursor usage, and annotations carry the safety profile. It omits the mutual-exclusion rules among `unanswered`, `relatedTo`, `linkedTo` and `hot`/`week`/`month`, and gives no routing against the several sibling question-listing tools.

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 explains every parameter, including the `hot`/`week`/`month` incompatibilities and cursor reuse rules. The description merely enumerates parameter names plus "7 more," adding no semantics beyond the structured fields.

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 ("List Stack Overflow questions") and enumerates the filtering axes: tag, time range, votes/activity, and related/linked questions. That is enough to distinguish it from title-only or batch-retrieval siblings, but it never names those siblings 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?

Usage is implied by the filter list rather than stated: an agent can guess this is the broad browsing tool, but nothing says when to prefer it over `stack_overflow_questions_search`, `stack_overflow_questions_title_search`, or `stack_overflow_user_questions_list`. No exclusions or prerequisites 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