Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Substack note

substack_note_get
Read-onlyIdempotent

Fetch a specific Substack note by its note ID to read or analyze the note content.

Instructions

Get a Substack note by id. Requires noteId.

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

Input Schema

NameRequiredDescriptionDefault
noteIdYesRequired. A note id as Substack displays it, e.g. `378007586`.
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.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully supplied by structured data. The description adds nothing beyond that — no note on what a note object contains, whether private/non-public notes are retrievable, or any auth/rate constraint — and its one clause merely restates the schema.

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?

Two short sentences with the purpose front-loaded and no filler. The second sentence is largely redundant with the schema's 'Required.' note on noteId, which is minor waste but not padding.

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 single-object fetch with a fully documented schema and complete annotations, the definition is minimally sufficient. However, with no output schema, an agent gets no indication of what a note record includes or how a missing/private note is signaled, which is a real gap for a retrieval tool.

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%, and the noteId schema entry already gives the format example (`378007586`) and required status, which is richer than the description. The description adds no meaning beyond the schema for noteId and says nothing about context, llm_model, or conversation_id, 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?

The description gives a concrete verb and resource ('Get a Substack note by id'), which is unambiguous and clearly distinct from the list-style siblings such as substack_note_replies_list or substack_notes_explore_list. It does not explicitly name a sibling or scope boundary, but the single-object-by-id framing is enough for an agent to route correctly.

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?

'Requires `noteId`' is a prerequisite, not when-to-use guidance. There is no statement about when to prefer this over the list siblings (e.g., replies/explore) or what to do if the id is unknown, so an agent gets no routing help beyond the name.

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