Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_techstack_search

Search the website tech-stack dataset for sites built with specific technologies. Apply AND/OR/NOT filters to refine results.

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
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the dataset structure and filter semantics but lacks details on pagination behavior, rate limiting, output format, or error handling. The description is informative but not fully comprehensive on behavioral traits.

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 a single paragraph that is front-loaded with the dataset purpose. It covers all necessary points without unnecessary verbosity. Slightly more structured formatting (e.g., bullet points for filter types) could improve readability, but it remains efficient.

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?

Given the complexity of 20 parameters and no output schema, the description covers the main usage patterns and filter logic well. It is mostly complete but could mention default values (e.g., run_id defaults to latest), pagination constraints, or return format to be fully comprehensive.

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?

Schema description coverage is 100%, so baseline is 3. The description adds significant value by explaining the reverse-index filter logic (AND, OR, NOT with technology, any_of, not) and providing an example. This goes beyond individual parameter descriptions to explain how they interact.

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 the tool searches the website tech-stack dataset, explains the dataset content (one record per site listing web technologies), and compares to BuiltWith/Wappalyzer. It does not explicitly distinguish from sibling tools like datasets_techstack_facets or datasets_techstack_item, but the search purpose is evident.

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 provides detailed usage guidance: how to use technology (AND), any_of (OR), and not (exclusion) filters, with an example. It explains the sort enum values and render_tier enum. However, it does not explicitly state when to use this vs siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server