Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack profile notes

substack_profile_notes_list
Read-onlyIdempotent

Retrieve a Substack reader's public Notes and replies by handle, with cursor pagination to review complete profile activity.

Instructions

List a Substack reader's public Notes and replies. Requires handle. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
typeNo`notes` for the person's own notes, `replies` for their replies, `all` for both.all
cursorNoOpaque cursor from the previous page's `nextCursor`.
handleYesRequired. A profile handle, e.g. `dieworkwear` or `@dieworkwear`.
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.5/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 that only public notes/replies are returned and that results may be paginated via cursor, which is useful but modest additional context.

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, front-loaded with the core action and followed by the key prerequisite and pagination note. No wasted wording, though it is quite terse.

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?

For a read-only paginated list tool with a fully documented schema and no output schema, the description covers the essentials. The conversation_id sequencing and analytics params are handled by the schema, so nothing critical is missing.

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 all six parameters (including the type enum and cursor semantics) are already documented in the schema. The description only restates the handle requirement and cursor usage, adding little beyond the schema; 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?

States a specific verb and resource: 'List a Substack reader's public Notes and replies.' An agent can tell it retrieves a profile's notes/replies, though it does not explicitly differentiate itself from siblings like substack_notes_explore_list or substack_note_replies_list.

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?

Gives a prerequisite ('Requires `handle`') and a pagination hint ('use cursor when paginated'), which implies usage context. However, it offers no explicit when-to-use vs. when-not guidance or named alternatives among the many sibling list tools.

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