Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Substack posts, notes and people

substack_search_top
Read-onlyIdempotent

Search Substack posts, notes, and profiles by query, then use a cursor to page through results for relevant content and authors.

Instructions

Search Substack posts, notes and profiles, cursor paged. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "substack_search_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Text to search posts, notes and profiles for.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only pagination behavior (cursor-paged, returns a list), which is modest but real value beyond 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?

A single front-loaded sentence with the resource scope stated first and paging second; nothing is repeated or padded. 'Requires query' and 'Returns a list' are slightly redundant with the schema and annotations but cost little.

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, open-world search with no output schema, the description covers scope, the required query and cursor-based pagination. The meta-parameters (context, llm_model, conversation_id) are fully specified in the schema, so the definition is adequately 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 all five parameters including the mandatory context, llm_model and conversation_id are documented in the schema itself. The description only restates that query is required and that cursor is for pagination, adding no meaning beyond the schema.

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 states a specific verb (Search) and resource set (Substack posts, notes and profiles), which matches the title and is unambiguous. It does not distinguish itself from siblings such as substack_search_profiles or substack_search_publications, which appear to cover narrower scopes.

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 guidance on when to choose this broad search over the narrower sibling search tools, and no stated exclusions. The only usage instruction is 'use cursor when paginated', which addresses paging rather than tool selection.

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