Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow post comments

stack_overflow_post_comments_list
Read-onlyIdempotent

Fetches every comment for a given Stack Overflow question or answer by post ID, returning the full comment list.

Instructions

List every comment on a Stack Overflow question or answer. Requires postId. Returns a list.

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_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds only that the result is a list, and says nothing about pagination, ordering, or whether deleted/flagged comments are filtered. Given annotated safety, a 3 is fair but the extra behavioral value is thin.

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?

Three short sentences, front-loaded with the operation and resource, with zero padding. 'Returns a list' is the weakest line — vague and adding little — but it does gesture at output shape in the absence of an output schema.

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 five-parameter tool with three required params (including analytics plumbing) and no output schema, the description covers only the core operation. Pagination behavior, comment ordering, and whether answer comments are included are all unaddressed, leaving gaps an agent would hit on first use.

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 postId, site, and the analytics parameters are fully documented in the schema itself. The description merely repeats that postId is required and says nothing about site selection or how the context/llm_model/conversation_id fields affect the call. 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 gives a specific verb and resource: 'List every comment on a Stack Overflow question or answer.' This distinguishes it reasonably from user-oriented siblings like stack_overflow_user_comments_list, though it never names an alternative. It is clear what the tool retrieves, but the sibling differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Requires `postId`' is a prerequisite restated from the schema, not when-to-use guidance. There is no mention of when to prefer this over stack_overflow_user_comments_list or the batch variant, and no exclusions or preconditions beyond the required id.

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