Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack profile posts

substack_profile_posts_list
Read-onlyIdempotent

Lists posts published by a Substack reader profile using a handle, with cursor pagination to retrieve additional results.

Instructions

List the posts a Substack reader published. 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_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return, 1 to 50. No further posts are available past this limit, so use 50 to get all that are available.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only that it returns a list and that a cursor is used for pagination — useful but thin, with no mention of result ordering or what a post object contains.

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?

Three short, front-loaded sentences with no filler. Minor redundancy in restating "Requires `handle`", which the schema already marks as required, but nothing bloats the definition.

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 a fully documented schema and no output schema, the description covers the essentials. It stops short of describing the returned post fields or how pagination terminates, which would help an agent chain calls.

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 handle format, limit bounds, and cursor semantics. The description merely restates the handle requirement and gestures at the cursor, adding no meaning beyond structured fields; 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 the posts a Substack reader published") and the scope word "reader" implicitly separates it from publication-level siblings. It is clear, but never names a sibling to sharpen the distinction between profile posts and publication posts.

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 or when-not-use guidance and no alternative named. An agent must infer the choice between this and substack_publication_posts_list or substack_profile_get on its own; only the prerequisite "Requires `handle`" is given.

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