Crawlora MCP

datasets_substack_item

Read-only

Fetch one stored Substack writer profile or publication by the exact uid returned by datasets_substack_search: user: or publication:. Returns a validated public snapshot; absent or unvalidated rows return 404. Inspect hydrated_at for capture time; this does not perform a live lookup. Use datasets_substack_search to find a uid.

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": {
      "uid": "<uid>"
    },
    "name": "datasets_substack_item"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	required,Exact dataset row UID returned by search: user:<handle> or publication:<host>.

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.

AddedNov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real context beyond readOnlyHint/openWorldHint: absent or unvalidated rows return 404, and hydrated_at signals capture time, so the agent knows to check freshness rather than expect live data. Missing any rate-limit or snapshot-vs-current-data caveats beyond hydration, but the behavior surface is well covered.

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 tight sentences, front-loaded with the primary action, then validation semantics, then the pointer to the search sibling. No filler, though the uid format appears twice (once in prose, once in 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?

An output schema exists so return values need no explanation, and the description covers the key unknowns: uid provenance, 404 on missing/unvalidated rows, and snapshot freshness. Nothing an agent needs to call it correctly is missing.

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% and the uid description already states the format, yet the description restates and reinforces the exact user:<handle> / publication:<host> pattern, which is the highest-risk failure mode for this call. Marginal added value over schema, but appropriately so.

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: fetch one stored Substack writer profile or publication by exact uid, with the two accepted uid forms spelled out. It is clearly distinguishable from datasets_substack_search, which produces the uid.

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

Usage Guidelines5/5

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

Explicitly says to use datasets_substack_search to find a uid, and explicitly says this tool does not perform a live lookup, which rules out the most likely mis-invocation. When-to-use and when-not-to-use are both present.

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?