Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_llms_search

Search the AI-readiness (llms.txt) dataset. Searches the AI-readiness census of the top 1M sites (dataset id enum value llms) — one record per site describing whether it serves a real /llms.txt or /llms-full.txt (who produced it…

Instructions

Search the AI-readiness (llms.txt) dataset. Searches the AI-readiness census of the top 1M sites (dataset id enum value llms) — one record per site describing whether it serves a real /llms.txt or /llms-full.txt (who produced it, what it links to and mentions) and what its /robots.txt says to 17 AI crawlers, next to a homepage control request. Search results omit the file bodies; read one site with the item endpoint. blocked and error states mean unknown, never absent. Sort enum: relevance, rank_asc, links_desc, bytes_desc, domain_asc, crawled_desc. state and robots_state enum: present, absent, blocked, error, skipped. source_kind enum: shopify_agent_template, seo_plugin, platform_default, parked, custom. generator enum: yoast, aioseo, rankmath, wix, shopify, parked. robots_default enum: allowed, partial, blocked. content_signal_train enum: yes, no. Crawler enum for blocks_all, blocks_any and not_blocked: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Bytespider, Applebot-Extended, Amazonbot, meta-externalagent, cohere-ai, Diffbot. Site owners can ask for removal at privacy@crawlora.net. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoSubstring match on the site domain, max 256 characters
botNoAI crawler named inside a valid /llms.txt, e.g. GPTBot (see facet=bot for the values)
tldNoExact top-level-domain filter, e.g. com, org, io
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rank_asc, links_desc, bytes_desc, domain_asc, crawled_desc
textNoFull-text match on the /llms.txt title and summary, max 256 characters
stateNo/llms.txt state. Enum: present, absent, blocked, error, skipped. blocked and error mean unknown, not absent
validNotrue keeps only sites serving a valid /llms.txt, false keeps the rest
run_idNoScan run id; defaults to the latest run
categoryNoExact category label carried by the source list; the top-1M run has none, so this is empty for it
generatorNoGenerator detected in a valid /llms.txt. Enum: yoast, aioseo, rankmath, wix, shopify, parked
injectionNotrue keeps only valid /llms.txt files containing instruction-override text aimed at AI readers
min_linksNoMinimum number of links in a valid /llms.txt, 0 or greater
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
reachableNotrue keeps only sites whose homepage control request answered, false only sites that did not
blocks_allNoRepeatable AI crawler that robots.txt must block (AND). Enum: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Bytespider, Applebot-Extended, Amazonbot, meta-externalagent, cohere-ai, Diffbot
blocks_anyNoRepeatable AI crawler; robots.txt must block at least one (OR). Enum: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Bytespider, Applebot-Extended, Amazonbot, meta-externalagent, cohere-ai, Diffbot
full_validNotrue keeps only sites serving a valid /llms-full.txt
not_blockedNoRepeatable AI crawler that robots.txt must NOT block. Enum: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Bytespider, Applebot-Extended, Amazonbot, meta-externalagent, cohere-ai, Diffbot
placeholderNotrue keeps only valid /llms.txt files that still hold template placeholder text
source_kindNoProducer of a valid /llms.txt. Enum: shopify_agent_template, seo_plugin, platform_default, parked, custom
home_blockedNotrue keeps only sites whose homepage was walled off from the scan (a block or challenge)
mentions_mcpNotrue keeps only valid /llms.txt files that mention the Model Context Protocol
robots_stateNo/robots.txt state. Enum: present, absent, blocked, error, skipped
all_ai_blockedNotrue keeps only sites whose robots.txt blocks all 17 tracked AI crawlers
robots_defaultNoDefault stance of robots.txt toward AI crawlers. Enum: allowed, partial, blocked
mentions_openapiNotrue keeps only valid /llms.txt files that mention OpenAPI or Swagger
is_infrastructureNofalse (the common case) excludes backend CDN/DNS/cloud-vendor hostnames that rank highly but serve no public homepage; true keeps only those
min_train_blockedNoMinimum number of AI training crawlers (of 11 tracked) that robots.txt blocks, 0 or greater
content_signal_trainNoContent-Signal ai-train value declared in robots.txt. Enum: yes, no

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.9/5.0
Behavior4/5

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

No annotations, so the description carries full behavioral burden and does well: it discloses billing (1 credit/record, min 2, empty result costs 2, full page 100), that results omit file bodies, that blocked/error states mean unknown not absent, and a removal contact. It doesn't describe pagination limits or auth requirements, so below 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and usage well, but spends a large fraction of the text re-listing enum values (sort, state, source_kind, generator, robots_default, content_signal_train, crawler lists) that are already fully documented in the schema. This is bloated relative to value added.

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 30-parameter search tool with no output schema and no annotations, the description covers dataset scope, return-shape caveats, state semantics, billing, and query-vs-read routing. It's substantially complete, though it could say more about pagination bounds and result shape (fields returned).

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 coverage is 100%, so the baseline is 3; the description adds genuine semantic value beyond the schema by explaining that "blocked" and "error" mean unknown rather than absent, and enumerating the sort/state/source_kind/generator enums. It doesn't clarify every parameter or the combination semantics (e.g., blocks_all AND vs blocks_any OR is in schema), so a 4.

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 and resource ('Search the AI-readiness (llms.txt) dataset') and describes the record contents precisely (whether each site serves a real /llms.txt, who produced it, robots.txt crawler stance). It does not name or contrast the sibling datasets_llms_item or datasets_llms_facets, so it falls short of a 5.

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?

Clearly routes the agent: 'read one site with the item endpoint' and 'Search results omit the file bodies,' which tells the agent when to use search vs. item lookup. It lacks explicit when-not-to-use guidance or mention of the facets sibling, so not a 5.

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