Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack post reactors

substack_post_reactors_list
Read-onlyIdempotent

Retrieve the list of people who reacted to a Substack post by providing its numeric ID or URL. Use it to identify post engagement and audience reactions.

Instructions

List the people who reacted to a Substack post. Requires post. 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": {
      "post": "<post>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_post_reactors_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesRequired. A post: its numeric id (`223208969`) or its URL (`https://www.astralcodexten.com/p/...`). Post comments need the URL form.
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, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only 'Returns a list', which is vague, and says nothing about pagination, result ordering, empty-result behavior, or whether reactors include notes/restacks. With annotations present the bar is lower, so a 3 is fair.

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, front-loaded sentences with no filler. The trailing 'Returns a list' is close to wasted text given how little it conveys, but the overall structure is clean and scannable.

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?

There is no output schema, so the description carries responsibility for describing what comes back, and 'Returns a list' does not say what a reactor record contains or whether results are paginated. For a simple read-only list tool with fully documented parameters this is minimally adequate, but the sibling ambiguity and thin return description leave gaps.

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%, including detailed guidance on the `post` id-vs-URL forms and the required context/llm_model/conversation_id fields. The description only restates that `post` is required, adding no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource: 'List the people who reacted to a Substack post.' An agent can tell what it retrieves. However, it does not distinguish itself from close siblings such as substack_post_restackers_list or substack_post_comments_list, so the boundary between 'reactors' and adjacent engagement lists is left ambiguous.

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 `post`', which is a prerequisite already declared by the schema's required array. There is no statement of when to choose this over restackers, comments, or other post-related siblings, and no exclusions or conditions are offered.

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