Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack recommended publications

substack_publication_recommendations_list
Read-onlyIdempotent

Lists the publications a Substack publication recommends, so you can discover related newsletters and map recommendation networks.

Instructions

List the publications a Substack publication recommends. Requires publication. 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": {
      "publication": "<publication>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_publication_recommendations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRecommendations to return, 1 to 99.
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.
publicationYesRequired. A publication: its numeric id (`89120`), its Substack subdomain (`astralcodexten`), its host (`www.astralcodexten.com`) or its URL. A numeric id is refused with a 400 on the routes that need a subdomain, host or URL.
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?

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds only that the tool requires `publication` and returns a list; it does not discuss recommendation ordering, pagination, rate limits, or what the list contains, so it provides limited value beyond the supplied annotations.

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?

The description is two short sentences and is front-loaded with the core action. 'Requires `publication`' is somewhat redundant with the schema, and 'Returns a list' is generic, but there is no wasted prose.

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 simple read-only list tool with rich annotations and complete schema descriptions, the definition is mostly sufficient for invocation. However, it lacks guidance on when to use it versus sibling tools and, since there is no output schema, does not describe what the returned list items contain.

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 `publication`, `limit`, `context`, `llm_model`, and `conversation_id` in detail. The description adds no parameter meaning beyond repeating that `publication` is required, so the high-coverage baseline of 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 states a specific verb and resource: list the publications that a given Substack publication recommends. That is clear enough to separate it from generic publication or post listing tools, but it does not explicitly differentiate itself from sibling alternatives such as search or category-based publication lists.

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 that `publication` is required. It does not explain when to choose this tool over sibling tools like publication search, category publication lists, or profile subscriptions, nor does it state any exclusions or preconditions beyond the required parameter.

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