Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_substack_item

Retrieve a stored Substack profile or publication snapshot by exact dataset UID; use hydration timestamps to check staleness and confirm validated public identity.

Instructions

Get one stored Substack profile or publication. Retrieves one profile or publication snapshot that passed public identity validation when hydrated. Use the exact uid returned by datasets_substack_search. Missing, partial, and unvalidated rows return 404. Snapshots can become stale; inspect hydrated_at.

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

NameRequiredDescriptionDefault
uidYesDataset row UID: user:<handle> or publication:<host>, max 320 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the validation gate on stored rows, the 404 outcome for missing/partial/unvalidated rows, and staleness risk with the `hydrated_at` field to inspect. It omits auth requirements, rate limits, and response shape, but the failure-mode disclosure is unusually concrete.

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?

Four short sentences, front-loaded with the action, followed by validation/failure and staleness caveats in that order. Every sentence carries information; only minor redundancy between 'Get one stored' and 'Retrieves one ... snapshot' softens it.

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 single-parameter read tool with no output schema, the description covers what it returns conceptually, its key failure mode, and data-freshness caveats. Lacking any statement of the returned record shape or the auth/pagination context, it is strong but not exhaustive.

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 uid format (user:<handle> or publication:<host>, max 320 chars) is fully documented in the schema, so the baseline of 3 applies. The description adds provenance ('exact uid returned by datasets_substack_search') but no new format or validation detail beyond that.

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 ('Get one stored Substack profile or publication') and clarifies it returns a stored snapshot rather than live data. The distinction from the sibling search tool is implicit in the fetch-one framing and made explicit in the next sentence.

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?

Explicitly tells the agent where the input comes from ('Use the exact `uid` returned by `datasets_substack_search'), which is the key usage prerequisite. It does not spell out when-not to use it or what an agent should do instead if the uid is unknown, so it stops short of full routing guidance.

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

Deploy Server

Other Tools