Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack explore feed

substack_notes_explore_list
Read-onlyIdempotent

Fetch the public Substack explore feed of notes and posts; use the optional cursor to retrieve the next page of results.

Instructions

List the public Substack explore feed of notes and posts. Optional inputs: cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_notes_explore_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from the previous page's `nextCursor`.
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 readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the feed is public and contains both notes and posts, plus a pagination hint, but says nothing about result ordering, page size, rate limits, or authentication. Useful but thin on top of the annotations.

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 tight sentences with the core purpose front-loaded and no filler. The trailing parenthetical about cursors is mildly redundant with the schema but costs little.

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?

With no output schema, the description's 'Returns a list' is the only signal about the return shape, and it does not describe the item structure an agent would receive. For a simple read-only list tool with full annotations the bar is low, but this leaves the return value under-explained.

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 four parameters, including the conversation_id echo rule, are fully documented in structured fields. The description singles out cursor but only restates what the schema already says. Baseline 3 is appropriate since the schema carries the load.

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 names a specific verb and resource: 'List the public Substack explore feed of notes and posts.' That is clearly distinct from profile-scoped siblings like substack_profile_notes_list. However, it never distinguishes itself from discovery siblings such as substack_search_top or substack_publication_feed_get, so an agent must infer the boundary.

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 statement of when to call this versus the search or publication-feed siblings. The only instruction, 'use cursor when paginated,' is pagination mechanics rather than tool selection. An agent is left to guess whether the explore feed or a search endpoint is the right discovery surface.

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