Skip to main content
Glama

FoxAPIs data sources

Substack post

substack_post
Read-onlyIdempotent

A Substack post: title, publication, subtitle, word count, tags and paywall type, from its link. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "url": "<url>"
    },
    "name": "substack_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://www.lennysnewsletter.com/p/how-to-build-product-sense"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new operational facts: a 2-credit cost per call, no charge when the answer contains no data, and the need for a FoxAPIs key. It does not describe error or invalid-URL behavior, which keeps it from a 5.

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 tight sentences: the first front-loads what is returned, the second bundles cost and auth prerequisites. No filler or repetition.

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 no output schema, the description usefully enumerates the returned fields, and it discloses cost and credential requirements. Remaining gaps are minor: behavior on non-Substack URLs or failures, and how it relates to substack_publication.

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 schema's own example URL already shows the expected format, so the description's 'from its link' phrasing adds little beyond confirming the single url parameter points at a Substack post. Baseline 3 is appropriate when the schema carries the parameter detail.

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 resource (a Substack post) and enumerates the fields it returns — title, publication, subtitle, word count, tags, paywall type — taken from a post link. That distinguishes it from the sibling substack_publication well enough, though the retrieval verb itself is only implied by 'from its link'.

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: supply a Substack post URL to get that post's metadata. There is no explicit when-to-use versus when-not framing and no mention of the substack_publication sibling, so an agent must infer the boundary between post-level and publication-level lookups.

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.

Resources