Crawlora MCP

datasets_techstack_search

Read-only

Search the website tech-stack dataset — find sites by the technologies they use (repeat technology for AND, any_of for OR, not to exclude). Costs 1 credit per record returned (minimum 2), so keep page_size to what you need.

Input Schema

Name	Required	Description
`q`	No	Optional substring match on the site domain, max 256 characters.
`cdn`	No	Optional exact CDN / hosting filter, e.g. Cloudflare, Fastly, Vercel.
`cms`	No	Optional exact CMS filter, e.g. WordPress, Shopify, Webflow.
`not`	No	Repeatable exact technology name the site must NOT use (excludes).
`tld`	No	Optional exact top-level-domain filter, e.g. com, org, io.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: relevance, rank_asc, tech_count_desc, domain_asc, crawled_desc. Defaults to relevance with q, otherwise rank_asc.
`any_of`	No	Repeatable exact technology name; the site must use AT LEAST ONE (OR).
`run_id`	No	Optional scan run id; defaults to the latest run.
`category`	No	Optional exact category filter, e.g. Ecommerce, CMS, Analytics, Payment, CDN.
`ecommerce`	No	Optional exact e-commerce platform filter, e.g. Shopify, WooCommerce, Magento.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`reachable`	No	Optional filter; true keeps only sites whose homepage was fetched, false only sites that could not be fetched.
`technology`	No	Repeatable exact technology name the site MUST use (AND across all values), e.g. technology=Shopify&technology=Klaviyo. Use the names returned by search.
`web_server`	No	Optional exact web-server filter, e.g. nginx, Apache, IIS.
`has_captcha`	No	Optional filter; true keeps only sites with a detected CAPTCHA.
`render_tier`	No	Optional fetch-tier filter. Allowed values: http, browser.
`seed_source`	No	Optional source filter for where the domain was discovered, e.g. tranco.
`min_tech_count`	No	Optional minimum number of detected technologies, 0 or greater.
`server_language`	No	Optional exact server language / framework filter, e.g. PHP, ASP.NET, Ruby on Rails.
`is_infrastructure`	No	Optional filter; 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.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description goes beyond that by disclosing the billing model (1 credit per record, minimum 2), which is genuinely decision-relevant context absent from the structured fields.

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?

Two sentences, front-loaded with the capability and scoping rule, ending on a practical cost/pagination warning. No filler sentences.

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 a 21-parameter tool the description is fairly thin, though annotations cover safety, an output schema covers return values, and the schema covers parameters. Gaps remain around defaults, run_id behavior, and how this relates to sibling tools.

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 the schema already documents all 21 parameters, including the AND/OR/exclude semantics. The description's technology/any_of/not explanation largely restates what the schema says, so it earns only the baseline.

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?

States a specific verb (Search) and resource (website tech-stack dataset) and clarifies the core capability: finding sites by the technologies they use. It distinguishes from generic web search, though it does not explicitly differentiate from siblings 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains filter-combination semantics (repeat technology for AND, any_of for OR, not to exclude), which helps construct a query, and the cost note nudges page_size discipline. However, it gives no guidance on when to use this versus the item/facets siblings or the web_techstack tool.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.