Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack post restackers

substack_post_restackers_list
Read-onlyIdempotent

Lists the people who restacked a Substack post. Provide a post ID or URL to retrieve everyone who shared it, useful for tracking reach and identifying amplifiers.

Instructions

List the people who restacked 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_restackers_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

C2.8/5.0
Behavior2/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 only 'Returns a list', which conveys nothing about pagination, result ordering, empty-result behavior, or what a restacker record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded and free of filler words. However, 'Returns a list' is close to tautological for a tool named ..._list and does not earn its place the way a pagination or format note would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries responsibility for describing the return value — yet it only says 'Returns a list' without field names, ordering, or limits. For a listing tool with four parameters and no output schema, this leaves the agent guessing about what it will actually receive.

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 the numeric-id-vs-URL forms of `post` and the analytics-only `llm_model` — is already documented in the schema. The description's 'Requires `post`' merely repeats what the schema marks as required, adding no new meaning.

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: 'List the people who restacked a Substack post.' Combined with the name, an agent can tell this targets restackers rather than reactors or commenters, though it does not explicitly name the closest sibling (substack_post_reactors_list).

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?

There is no when-to-use guidance, no when-not-to-use, and no reference to alternatives such as the reactors or comments lists. The only guidance is 'Requires `post`', which is a prerequisite, not usage context.

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