Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack profile subscriptions

substack_profile_subscriptions_list
Read-onlyIdempotent

List the publications a Substack reader publicly subscribes to by handle, returning a paginated list with cursor support.

Instructions

List the publications a Substack reader shows publicly. 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_subscriptions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond them by disclosing that only public subscriptions are returned and that pagination is cursor-based. It does not describe ordering or result shape in detail, but the annotations lower the bar.

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?

Three short sentences, front-loaded with the resource and scope, followed by the prerequisite and return/pagination hint. No sentence is wasted or redundant.

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 signals that the result is a list and that pagination should be followed with the cursor. For a simple read-only list tool with full schema coverage and rich annotations, this is nearly complete, though visibility rules beyond 'publicly' remain unspecified.

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 every parameter including cursor, context, and llm_model is already documented. The description's mention of `handle` and cursor merely restates the schema rather than adding syntax or behavioral nuance. Baseline 3 is appropriate.

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 publications a Substack reader shows publicly. The 'publicly' qualifier distinguishes it from a private-subscription lookup, though it does not explicitly contrast with siblings such as substack_profile_posts_list or substack_profile_notes_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?

The prerequisite 'Requires `handle`' is stated, and the resource type implies when the tool applies. However, there is no explicit when-not guidance or pointer to an alternative for private subscriptions or other profile data, leaving usage to inference.

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