Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_scrape

Destructive

Retrieve a webpage through Nstdata Crawl to extract content in markdown, HTML, links, PDF, screenshot, or raw data; creates a potentially billable scrape task.

Instructions

Retrieve a webpage through Nstdata Crawl. Creates a potentially billable scrape task.

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": "nstdata_crawl_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget HTTP(S) URL without embedded credentials. For a site crawl this is the single seed URL.
modeNosync waits for the single-page response; async returns a task id to resume with nstdata_crawl_scrape_result. Neither mode retries submission.sync
formatsNoRequested output formats. Large results may contain storage references instead of inline content.
optionsNoOptional Crawl service settings. Set onlyMainContent=false when full-page navigation is needed for link discovery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered; the description's "potentially billable" adds genuinely new cost context that annotations do not express. However it omits other behavioral facts an agent needs, such as the absence of automatic retries on submission and which tool to call afterward in async mode.

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 short sentences, front-loaded with the action and immediately followed by the cost caveat. There is no filler, hedging, or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with nested crawl options and an async task model, the description is thin: it never mentions that async returns a task id, nor which sibling resolves it, nor the absence of retries. The rich schema prevents this from being a blocking gap, but the description alone would leave an agent guessing about the result path.

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 the four parameters and the deeply nested options object are already fully self-documenting, including the enum values for mode and formats. The description adds nothing beyond the schema and does not even hint at the sync/async parameter that most affects usage.

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?

"Retrieve a webpage through Nstdata Crawl" states a specific verb (retrieve) and resource (webpage) via a named service, which is clear enough to act on. It never distinguishes itself from siblings such as nstdata_crawl_scrape_result or nstdata_crawl_start, even though the sibling name suggests a paired result-retrieval tool.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, and no routing to alternatives. The important sync-vs-async decision and the pointer to nstdata_crawl_scrape_result for resuming appear only in the schema's mode description, not in the tool description an agent reads first.

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