Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Substack publications

substack_search_publications
Read-onlyIdempotent

Search Substack publications and metadata by query; get a paginated list of matching publications.

Instructions

Search Substack publications and their metadata. Requires query. Returns a list (use page 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_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 0 to 100,000; twenty publications a page. Only pages 0 to 3 have results, so a page past 3 returns an empty list with `hasMore: false`.
queryYesRequired. Text to search publications for.
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 readOnly, idempotent, openWorld, and non-destructive, so the safety profile needs no restating. The description adds that the result is a list and hints at paging, but omits the significant behavioral caveat that only pages 0-3 return data (left entirely to the schema's page property).

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 purpose followed by the return shape. 'Requires `query`' is filler since the required array already enforces it, but there is no other waste.

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 a fully documented 5-parameter schema and rich annotations, most of the burden is already met. However, for a five-parameter search tool sitting among four other search siblings, the description provides no disambiguation and no explanation of what 'publications and their metadata' results actually contain.

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%, including the unusual required params (context, llm_model, conversation_id) and the page-range caveat, so the schema carries the burden. The description only echoes that query is required and gestures at page, adding essentially no meaning beyond the structured fields.

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 ('Search Substack publications and their metadata'), which is unambiguous on its own. It does not differentiate from near-neighbors such as substack_search_top, substack_search_profiles, or substack_categories_publications_list, leaving the agent to infer from names alone.

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?

The only guidance is 'Requires `query`' — which is parameter restatement already enforced by the required array — and a parenthetical about pagination. There is no statement of when to choose this over the other search and category-listing siblings, and no exclusions.

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