Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Substack profiles

substack_search_profiles
Read-onlyIdempotent

Search Substack profiles using a text query to identify authors or publications that match specific keywords. Returns paginated results for profile discovery and outreach research.

Instructions

Search Substack profiles by text. 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_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 0 to 100,000; twenty profiles 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 profiles 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 this is a read-only, idempotent, open-world, non-destructive operation, so the safety profile is carried. The description adds only a light return-shape note ('returns a list'), while the genuinely useful behavioral fact — that only pages 0–3 yield results before an empty list with hasMore:false — lives in the schema rather than the description.

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?

Three short sentences with the core action front-loaded and no wasted prose. 'Requires query' is mildly redundant with the schema's required list, which is the only real trim available.

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 simple filtered search with full schema coverage and rich annotations, the description covers purpose and return shape adequately. The one gap is the practical result ceiling implied by pagination, which the schema covers but the description only hints at with 'when paginated'.

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 query, page, context, llm_model, and conversation_id is already documented in the schema. The description restates that query is required and gestures at page, adding no syntax or semantics beyond structured data; baseline 3 applies.

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 profiles by text'), which clearly separates it from sibling content searches such as substack_search_publications or substack_search_podcasts. It stops short of explicitly naming an alternative, but the resource noun does the disambiguating work.

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 'use page when paginated', which is a procedural hint rather than a when-to-use rule. There is no statement of when a profile search is preferable to a publication, post, or podcast search, and no prerequisites or exclusions are given.

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