Crawlora MCP

substack_user_connections

Read-only

List a Substack user's followers, following, or subscribers. Each entry is a full profile in the same shape as substack_user, subscriber signals included. user_id is the numeric id from substack_user. The upstream returns a bounded preview of each list rather than complete membership.

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_connections"
  }
}

Input Schema

Name	Required	Description	Default
`list`	No	Which list to read: followers, following, or subscribers. Defaults to followers.
`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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: each entry is a full profile, subscriber signals are included, and the upstream returns only a bounded preview rather than complete membership. That last point is important for an agent interpreting result completeness.

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?

Three sentences, front-loaded with the core operation and each sentence carrying distinct information (shape, id source, preview limitation). No filler, though the id-source sentence partially duplicates the schema.

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 structure need not be explained, and the description still notes the shared shape and bounded preview. Combined with the annotations and 100% schema coverage, an agent has enough to call it correctly; only when-to-use guidance is thin.

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 both parameters are already documented with their meanings and the list default. The description largely restates the user_id source and list options rather than adding syntax or constraints beyond the schema, so the baseline 3 applies.

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 ('List a Substack user's followers, following, or subscribers') and specifies the scope of what is returned. An agent can distinguish this from substack_user or substack_user_activity 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 Guidelines3/5

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

The description gives a prerequisite (user_id comes from substack_user) but never states when to use this over sibling tools like substack_user_search or substack_user_activity. Usage is implied by the resource rather than explicitly framed.

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?