Skip to main content
Glama

Antigravity x402 & MCP Gateway

analyze_substack_newsletter

[0.005000 USDC via x402] Analyzes any public Substack newsletter or custom-domain Substack publication to extract recent posts, publishing cadence (posts/week), average likes/comments/restacks, outbound links, and probable sponsor/advertiser domains.

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": {
      "publication": "<publication>"
    },
    "name": "analyze_substack_newsletter"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_postsNoMaximum number of recent archive posts to analyze (1 to 12, default 5).
publicationYesSubstack subdomain, handle, or custom domain URL (e.g., 'importai.substack.com').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two useful traits: the call is billed at 0.005000 USDC via x402 and it only works on public publications. It says nothing about rate limits, failure modes for private or invalid publications, or whether the analysis is cached/realtime, which are material gaps for a paid network-fetching tool.

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?

One dense sentence with no filler, and the extracted-outputs list is informative rather than padding. The pricing bracket is placed ahead of the purpose, which slightly delays the core verb, but the whole thing is easy to scan.

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 3-parameter tool with no output schema, the description does the important compensating work by enumerating the exact fields returned, and it flags cost and the public-only constraint. What is missing is operational behavior on errors or payment failure, which the schema only partially covers via the payment-signature parameter.

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 the baseline is 3; every parameter including max_posts and the x402 payment signature is already documented in the schema. The description adds only the loose mapping of 'recent posts' to the analysis scope and does not clarify formats, defaults, or the payment flow beyond what the schema states.

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 names a specific verb ('Analyzes') and a precise resource ('any public Substack newsletter or custom-domain Substack publication'), then enumerates the exact signals returned (posts, cadence, likes/comments/restacks, links, sponsor domains). It is unambiguous what the tool does, though it never explicitly distinguishes itself from any alternative, relying on the siblings' obviously unrelated domains.

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 only implied: the word 'public' scopes it to public publications, and the price prefix signals a paid call. There is no explicit statement of when to prefer this over another tool, no mention of what happens with non-Substack domains, and no guidance on choosing max_posts values.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.