Skip to main content
Glama
Sign In
Scout MCP Server

Scout MCP Server

Official
by Scout-AI-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

scout_crawl

Crawl a website from a given start URL and return its pages, with an option to limit the number of pages and stay on the same host.

Instructions

Crawl a website from a start URL and return its pages. Bound it with max_pages.

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": {
      "start_url": "<start_url>"
    },
    "name": "scout_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_urlYesThe URL to start crawling from
max_pagesNoMaximum pages to crawl
same_host_onlyNoStay on the same host

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It does not mention crawling behavior (e.g., following links, respecting robots.txt, rate limits), return format, or mutability. The phrase 'return its pages' is vague.

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?

The description is very concise (one sentence). However, the phrasing 'Bound it with max_pages' is slightly awkward and could be clearer.

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

Completeness2/5

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

Given three parameters, no output schema, and no annotations, the description is too minimal. It fails to explain what 'pages' includes, any limitations, or how to use the tool effectively.

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 baseline is 3. The description adds minimal value beyond the schema; 'Bound it with max_pages' reinforces max_pages but doesn't clarify interpretation or constraints.

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 clearly states it crawls a website from a start URL and returns pages, which distinguishes it from sibling tools like scout_scrape (single page) and scout_search (search). However, it lacks explicit contrast with alternatives.

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?

No guidance is given on when to use this tool versus alternatives like scout_scrape or scout_extract. The only usage hint is 'Bound it with max_pages,' which is insufficient.

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