Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_list

Lists read-only stored scraped datasets with supported capabilities like search, detail, facets, nearby, history, trending, or changes; no live scrape is started.

Instructions

List stored scraped datasets. Lists the read-only scraped datasets available, with no parameters. Each item has its id, name, description and the capabilities it supports: search, detail, facets, nearby, history, trending or changes. It reads stored data and does not start a live scrape.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the operation read-only, states there are no parameters, and explicitly says it reads stored data without starting a live scrape (i.e., no side effects or network fetch). It omits any note on result size or pagination behavior, keeping it just under a 5.

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?

Information is front-loaded and the capability list is useful, but the opening two sentences are redundant ('List stored scraped datasets' vs 'Lists the read-only scraped datasets available'), which slightly dilutes an otherwise tight three-sentence description.

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

Completeness5/5

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

With no annotations and no output schema, the description compensates by documenting the shape of each returned item (id, name, description, supported capabilities), giving the agent enough to interpret the response without a schema.

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?

The tool has zero parameters, so the baseline is 4; there is nothing for the description to add beyond confirming that no parameters are required.

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?

Specific verb+resource ('List stored scraped datasets') with scope clarified as read-only and parameterless, which cleanly separates it from the parameterized datasets_* search/detail/facets siblings. The enumerated capability list further signals this is the catalog entry point rather than a data-fetch tool.

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?

The description conveys clear usage context ('read-only scraped datasets available', 'does not start a live scrape'), positioning it as a discovery step before the search/detail capabilities. It stops short of explicitly stating alternatives or when-not-to-use conditions, so it is strong but not exhaustive.

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