Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get comments on Stack Overflow posts

stack_overflow_posts_comments_batch_get
Read-onlyIdempotent

Fetch comments for up to 100 Stack Overflow questions or answers in one call by supplying post IDs, enabling batch comment review without separate requests.

Instructions

Get the comments on up to 100 Stack Overflow questions and answers in one call. Requires ids.

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": {
      "ids": "<ids>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_posts_comments_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Post (question or answer) ids, comma-separated, 1 to 100, e.g. `11227809,11227902`. Duplicates are dropped.
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.
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.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 fully covered. The description adds only the 100-id ceiling, which the schema also states, and says nothing about ordering, pagination, or behavior for invalid/deleted post ids.

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 short sentences, front-loaded with the action and the batch limit, with zero redundant wording.

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 batch fetch with full schema coverage and rich annotations, the description covers what the tool does and its scale limit. It is slightly thin on routing guidance relative to the many sibling comment/list tools, but nothing needed to invoke it correctly 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 description coverage is 100%, so every parameter including `ids`, `site`, `context`, `llm_model` and `conversation_id` is already documented in the schema. The description's 'Requires `ids`' adds no meaning beyond that, so the 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?

States a specific verb and resource ('Get the comments on ... questions and answers') plus the batch scope ('up to 100 ... in one call'), which distinguishes it from a single-post comment lister. It stops short of naming the sibling it replaces, so an agent must infer the batch-vs-single distinction.

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?

The only guidance is 'Requires `ids`', which restates the schema's required field. There is no statement of when to prefer this over stack_overflow_post_comments_list, no note on what happens with mixed question/answer ids, and no exclusions.

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