Crawlora MCP

substack_search

Read-only

Search posts across all of Substack and get the publications that also matched, unlike substack_publication_posts which searches within one publication. Set focus_publication_id to additionally receive that publication's own matching posts in focused_posts.

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>"
    },
    "name": "substack_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	Zero-based page. 20 posts per page.
`query`	Yes	Required search text.
`focus_limit`	No	Optional cap on focused_posts, 1-20. Requires focus_publication_id.
`focus_publication_id`	No	Optional numeric publication id. When set, focused_posts carries that publication's own matching posts alongside the site-wide results.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond that: the result set includes matching publications, and focus_publication_id changes the response shape by populating focused_posts. It does not mention pagination behavior, which is only implicit elsewhere.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences: the scope and sibling distinction come first, then the optional focus behavior. No filler or redundancy.

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?

With an output schema present, return values need not be explained, and the description covers routing and the focus mechanism. Minor omission: nothing states result volume/pagination expectations, though the page parameter's schema description addresses that.

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 coverage is 100%, so all four parameters are already documented, including focus_limit's 1-20 range and focus_publication_id's effect. The description's restatement of focus_publication_id semantics largely duplicates the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (posts across all of Substack) with explicit scope, then names the sibling substack_publication_posts and how it differs. An agent can route between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts against the alternative (site-wide vs within one publication) and gives the condition for the optional focus_publication_id to broaden results into focused_posts. Both when-to-use and when-to-use-the-sibling are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?