Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Substack publication directory

substack_directory_list
Read-onlyIdempotent

Lists Substack publication subdomains from numbered directory files with cursor-based paging and limits, so you can retrieve the directory in controlled batches.

Instructions

List Substack publication subdomains, one directory file at a time, cursor paged. Optional inputs: file, page, cursor and limit. 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_directory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoDirectory file, 1 to 24. Each file is a numbered slice of the directory, not a category.
pageNoPage number form, 0 to 100,000; `limit` entries a page. Prefer `cursor` for the next page.
limitNoEntries to return, 1 to 5,000.
cursorNoThe way to page: pass `page.nextCursor` from the previous response to get the next page. A directory cursor belongs to the file that issued it.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only that results come back as a list and that pagination should use cursors; it says nothing about total corpus size, whether all 24 files must be traversed to enumerate everything, or rate/consistency behavior for an open-world read.

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, with zero filler. The middle sentence that just enumerates parameter names is the one low-value element, but it 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 7 parameters, two of them required plumbing (context, llm_model, conversation_id) and no output schema, the description covers the calling mechanics adequately but leaves the enumeration model underspecified: it never says a full directory requires walking files 1-24 or what a returned entry contains. The rich schema compensates for the parameter side, so this is adequate rather than complete.

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 baseline is 3 and the description's mention of 'file, page, cursor and limit' merely restates the parameter names without added meaning. It does not supplement the schema's own explanation of the file-as-slice semantics or the cursor-belongs-to-file constraint, and it omits the required context/llm_model/conversation_id parameters entirely.

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 Substack publication subdomains') and adds a mild scope qualifier ('one directory file at a time, cursor paged'), so the agent knows this is a bulk directory enumeration rather than a search. It does not name a sibling such as substack_search_publications or substack_categories_publications_list to sharpen the distinction, so it falls short of a 5.

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?

Usage is only implied: the framing 'one directory file at a time' plus 'use cursor when paginated' tells the agent how to iterate, and the schema's own note to prefer cursor over page reinforces it. However, there is no explicit statement of when to choose this over the search or category-listing siblings, and no exclusion of any case.

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