Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow post revisions

stack_overflow_post_revisions_list
Read-onlyIdempotent

List a Stack Overflow post's revisions to compare the text before and after each edit. Provide the post ID and paginate with a cursor.

Instructions

List the versions of a Stack Overflow post, with the text before and after each edit. Requires postId. 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": {
      "postId": "<postId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_post_revisions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
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.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
postIdYesRequired. Post id (a question or an answer) on the chosen site, e.g. `11227902`.
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.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description still adds real value by disclosing what each row contains (before/after text of each edit) and the pagination affordance, beyond what the hints provide. It stops short of noting ordering, result caps, or auth, keeping it just under top marks.

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 tight sentences with zero filler, front-loading the resource and what it returns before the requirements and pagination note. Every clause carries information an agent needs.

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?

For a simple read-only list tool with full schema coverage and an output-schema-free signature, the description covers purpose, key content, and pagination adequately. It could say more about ordering or how the before/after fields relate to a revision, but nothing essential to correct invocation is missing.

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 fully documents postId, cursor, limit, site, and the analytics fields. The description merely restates that postId is required and cursor is used for paging; it adds no syntax, format, or edge-case 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?

A specific verb and resource ("List the versions of a Stack Overflow post") plus scope ("text before and after each edit") makes the returned data concrete. The resource is naturally distinct from siblings like post_comments_list or post_timeline_list, though the description never names an alternative to route between them.

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?

It states the hard prerequisite ("Requires `postId`") and gestures at pagination ("use cursor when paginated"). It gives no when-to-use/when-not guidance and does not tell an agent to prefer timeline or comments tools for other post metadata, leaving that inference to the caller.

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