Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow post timeline

stack_overflow_post_timeline_list
Read-onlyIdempotent

Retrieve a Stack Overflow post's event timeline—edits, locks, answers, comments, votes, and reviews—by post ID, with event filters and cursor pagination for audit or research.

Instructions

List everything that happened to a Stack Overflow post: edits, locks, answers, comments, votes and reviews. 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_timeline_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.
typesNoOnly these kinds of event, comma-separated: `answer`, `comment`, `history`, `review`, `vote`, `other`. Default: all.
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.5/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 adds that results are paginated and that a cursor should be used past page one, which is real behavioral value, but it says nothing about ordering, page-size behavior, rate limits, or what happens with an invalid/stale cursor.

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 resource and event coverage, then the requirement and return shape. No wasted wording, though "Returns a list (use cursor when paginated)" is slightly compressed to the point of being terse.

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 read-only paginated list tool with full schema coverage and complete annotations, the description supplies what the structured fields don't: the aggregate event scope and the pagination continuation hint. Missing detail on result ordering and on the relationship between filters and cursors is minor but non-trivial.

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 site, limit, types, cursor, postId and the instrumentation fields in detail. The description only restates that postId is required and that the cursor is for pagination, adding no filtering semantics (e.g., how types interacts with cursor) beyond the schema.

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 gives a specific verb+resource ("List everything that happened to a Stack Overflow post") and enumerates the event kinds covered — edits, locks, answers, comments, votes, reviews. That enumeration implicitly separates it from narrower siblings like stack_overflow_post_comments_list or stack_overflow_post_revisions_list, but no sibling is named, so the differentiation requires inference.

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 only implied: an agent can infer this is the tool for an aggregated activity view rather than a single event type. There is no explicit "use this instead of X" routing, no statement about when a narrower sibling is preferable, and no preconditions beyond the required postId.

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