Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Substack post

substack_post_get
Read-onlyIdempotent

Fetches a Substack post by numeric ID or URL, returning the full free body or the paid preview. Use it to read or quote a specific Substack article inside your editor.

Instructions

Get a Substack post by id or URL, with the full free body or paid preview. Requires post.

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

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

A3.7/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 covered. The description adds real value with 'full free body or paid preview', telling the agent that paywalled posts come back truncated to a preview — but it says nothing about authentication, rate limits, or error behavior for an openWorld tool.

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 resource and identifier forms, with zero filler 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?

With no output schema, the description usefully sketches what comes back (full body vs preview) for a single-post getter whose parameters are fully documented in schema. The remaining gap is operational context — paywall/auth edge cases — rather than anything that would prevent a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 documents the id-versus-URL forms and the analytics/conversation plumbing parameters. The description only restates the `post` requirement, so the baseline of 3 applies; the parenthetical about paid previews adds slight output-relevant nuance but no parameter detail.

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 a Substack post) plus the two accepted identifiers and what content is returned (full free body or paid preview). That is enough to separate it from sibling list tools such as substack_post_comments_list, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose: if you want a single Substack post, call this. There is no explicit when-not guidance and no reference to the neighboring post tools (note_get, profile_get, comments_list) that an agent might confuse it with.

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