Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_techstack_search

Search website tech-stack records to find sites by required, optional, or excluded technologies and filters like CMS, CDN, and e-commerce.

Instructions

Search the website tech-stack dataset. Searches the website tech-stack index (dataset id enum value techstack) — one record per site listing the web technologies it is built with (frameworks, CMS, e-commerce, analytics, CDNs, servers, and more), BuiltWith / Wappalyzer-style. The reverse-index filters are the point: repeat technology to require several at once (AND), any_of to match at least one (OR), and not to exclude — e.g. sites on Shopify and Klaviyo but not Recharge. Sort enum: relevance, rank_asc, tech_count_desc, domain_asc, crawled_desc. render_tier enum: http, browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSubstring match on the site domain, max 256 characters
cdnNoExact CDN / hosting filter, e.g. Cloudflare, Fastly, Vercel
cmsNoExact CMS filter, e.g. WordPress, Shopify, Webflow
notNoRepeatable exact technology name the site must NOT use (excludes)
tldNoExact top-level-domain filter, e.g. com, org, io
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rank_asc, tech_count_desc, domain_asc, crawled_desc
any_ofNoRepeatable exact technology name; the site must use at least one (OR)
run_idNoScan run id; defaults to the latest run
categoryNoExact category filter, e.g. Ecommerce, CMS, Analytics, Payment, CDN
ecommerceNoExact e-commerce platform filter, e.g. Shopify, WooCommerce, Magento
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
reachableNotrue keeps only sites whose homepage was fetched, false only sites that could not be fetched
technologyNoRepeatable exact technology name the site MUST use (AND), e.g. technology=Shopify&technology=Klaviyo
web_serverNoExact web-server filter, e.g. nginx, Apache, IIS
has_captchaNotrue keeps only sites with a detected CAPTCHA
render_tierNoFetch-tier filter. Enum: http, browser
seed_sourceNoSource filter for where the domain was discovered, e.g. tranco
min_tech_countNoMinimum number of detected technologies, 0 or greater
server_languageNoExact server language / framework filter, e.g. PHP, ASP.NET, Ruby on Rails
is_infrastructureNofalse (the common case) excludes backend CDN/DNS/cloud-vendor hostnames that rank highly but were never meant to serve a public homepage, keeping only real, human-navigable sites; true keeps only those backend hostnames

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.17.5
    • addedInput schema / properties / any_of / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / not / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / render_tier / enum
      Added value: +[
+  "http",
+  "browser"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "rank_asc",
+  "tech_count_desc",
+  "domain_asc",
+  "crawled_desc"
+]
    • addedInput schema / properties / technology / items
      Added value: +{
+  "type": "string"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / properties / is_infrastructure
      Added value: +{
+  "description": "false (the common case) excludes backend CDN/DNS/cloud-vendor hostnames that rank highly but were never meant to serve a public homepage, keeping only real, human-navigable sites; true keeps only those backend hostnames",
+  "type": "boolean"
+}
  3. Addedv1.5.0

TDQS

A4.2/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 it explains the dataset structure, reverse-index semantics, and available sort/render_tier enums. It does not discuss pagination limits, output shape, or rate limits, but for a read-only search tool the disclosed behavior is reasonably complete.

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 dense but mostly efficient, front-loading the dataset identity and then explaining filter semantics. The enum lists for sort and render_tier are partially redundant with the schema, but they are compact and help the agent avoid opening the schema.

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 21-parameter search tool with no output schema and no annotations, the description covers the core concepts: what the dataset contains, how filters combine, and the main enum options. It does not mention pagination constraints or all filter categories, but those are well documented in the schema itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds significant meaning beyond the schema: it explains the AND/OR/exclude semantics of technology, any_of, and not, and gives a concrete example. This is exactly the kind of cross-parameter behavior the schema alone does not convey.

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 identifies a specific resource: the website tech-stack dataset, with one record per site and technology fields. It is specific about what the tool searches, but it does not explicitly differentiate it from sibling tools like datasets_techstack_item or datasets_techstack_facets.

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 gives strong guidance on how to use the reverse-index filters: repeat technology for AND, use any_of for OR, and not for exclusion, with a concrete Shopify/Klaviyo/Recharge example. It does not state when not to use this tool or name alternatives.

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