SiteCheck Web Intel

Post archive of a beehiiv newsletter: newsletter name

search_beehiiv_newsletter

Read-only

Post archive of a beehiiv newsletter (by beehiiv subdomain, e.g. superhuman, or the newsletter's own domain if hosted on beehiiv): newsletter name, total posts, and per post title, subtitle, URL, publish time, authors, free/premium audience, tags and reading time, 10 per page, newest first. Optional word filter within the page. Public archive data, no key; post bodies are not returned. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "newsletter": "<newsletter>"
    },
    "name": "search_beehiiv_newsletter"
  }
}

Input Schema

Name	Required	Description
`q`	No	Words that must all appear in the title or subtitle (filters this page only; optional)
`page`	No	Archive page, 1 or more (default 1), 10 posts per page
`newsletter`	Yes	beehiiv subdomain (superhuman → superhuman.beehiiv.com) or the newsletter's domain/URL (e.g. www.superhuman.ai)

Output Schema

Name	Required	Description	Default
`page`	No
`count`	No
`posts`	No
`source`	No
`website`	No
`checkedAt`	No
`newsletter`	No
`totalPages`	No
`totalPosts`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses pagination (10 per page, newest first), that the word filter only applies within the current page, that post bodies are omitted, and that pricing is $0.002 USDC per successful call via x402 with failures uncharged. That pricing and filter-scope detail is genuinely useful context not present in 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?

Front-loaded with the core identity, with pricing and constraints in a short second sentence. The middle sentence is a long run-on enumerating per-post fields that partially duplicates the output schema, which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 archive search with an output schema and 3 params, everything an agent needs is present: accepted newsletter identifiers, paging model, filter scope, exclusions (no bodies), and cost model.

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% and the description mostly restates it (subdomain example 'superhuman', domain/URL input, within-page filter). It adds little beyond the schema, so the baseline 3 applies; no extra syntax or edge-case meaning is offered.

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 and resource — 'Post archive of a beehiiv newsletter' — and enumerates the newsletter-level and per-post fields returned, which clearly separates it from the generic news/search siblings like search_news_across_the_web or search_wechat_articles.

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 implied by the beehiiv-specific scope and by noting 'Public archive data, no key' and 'post bodies are not returned', which signals what it can and cannot do. However it never says when to prefer this over a sibling (e.g. an article extractor for full text), so guidance is implied rather than explicit.

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

All SiteCheck Web Intel 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?