Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_start

Destructive

Starts a bounded site crawl from a single seed URL and immediately returns a task ID, letting you set depth, page, and format limits for controlled web data collection.

Instructions

Start a bounded site crawl and return its task ID immediately.

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

Input Schema

NameRequiredDescriptionDefault
urlYesTarget HTTP(S) URL without embedded credentials. For a site crawl this is the single seed URL.
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.
maxDepthNoOptional service-side link-discovery depth limit; depth counting follows the Crawl service.
maxPagesNoPage-count upper bound, not a guarantee of that many pages. Check actual returned URLs and per-page results.
excludeUrlsNoOptional service-side exclude filters for discovered links.
ignoreQueryNoOptional service-side query-string handling setting.
includeUrlsNoOptional service-side include filters for discovered links. These are not extra seed URLs or a batch scrape list.

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?

The annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuine value by disclosing the async contract ('return its task ID immediately'), implying each call launches a new job. It says nothing about cost, rate limits, or that a crawl reaches external sites.

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?

A single front-loaded sentence with zero waste: action, scope, and return behavior in order of importance.

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 an 8-parameter async job-launcher with no output schema, the description omits the critical follow-up flow — where the task ID is used and how to retrieve results. Annotations cover safety, but the workflow gap limits completeness to adequate.

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% and the nested options object is documented in exhaustive detail, so the schema carries the load. 'Bounded' loosely signals maxDepth/maxPages, but the description adds no meaning beyond the schema — notably it does not clarify seed-URL versus includeUrls semantics.

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?

The description states a specific verb and resource ('Start a bounded site crawl') and adds the key outcome that a task ID comes back immediately. It implicitly distinguishes itself from the scrape siblings, but it never names them, so the boundary is inferred rather than stated.

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?

There is no explicit when-to-use guidance versus nstdata_crawl_scrape, nstdata_crawl_pages or nstdata_crawl_status, and no mention that the returned task ID must be polled via a status tool and results fetched via a read tool. Only 'bounded' hints at the depth/page limits.

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