Crawlora MCP

substack_user_activity

Read-only

A Substack user's public activity feed: the notes they wrote, posts they published, and things they liked, replied to, or restacked. types is an optional comma-separated filter over note, post, like, replies, restack -- omit it for the default mixed feed. Cursor-paginated. Each item's kind is the upstream's own finer-grained label, so asking for restack returns both comment_restack and post_restack.

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": {
      "user_id": "<user_id>"
    },
    "name": "substack_user_activity"
  }
}

Input Schema

Name	Required	Description
`types`	No	Optional comma-separated activity kinds to include: note, post, like, replies, restack. Omit for the user's default mixed activity.
`cursor`	No	Opaque cursor from a previous response's next_cursor.
`user_id`	Yes	Required numeric user id, as returned by /substack/user.

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=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses cursor-pagination and the subtle fact that returned items carry the upstream's finer-grained kind label. It doesn't discuss filtering limits or auth, but the added context is meaningful.

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?

It is front-loaded with the purpose, then layers filter behavior, pagination, and the label nuance. Every sentence carries information, though the final sentence is dense. Well-sized with no filler.

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?

An output schema exists, so return values need not be described, yet the description still adds the important nuance about item kinds. Combined with the 100% parameter coverage and annotations, an agent has everything needed to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description exceeds it by clarifying the value-space behavior: that 'restack' expands to both comment_restack and post_restack, which the schema's enum-less string field cannot express. This is meaningful semantics beyond the schema.

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?

The description opens with a specific verb+resource ('A Substack user's public activity feed') and enumerates exactly what it contains (notes, posts, likes, replies, restacks). This clearly distinguishes it from siblings like substack_note, substack_notes, or substack_user without opening any schema.

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

Usage Guidelines4/5

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

It explains how to use the types filter and states the default behavior when omitted ('omit it for the default mixed feed'), which is real usage guidance. However, it does not explicitly point to an alternative tool for the sub-feeds (e.g., substack_note) or state exclusions, so it stops short of full when/when-not routing.

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?