Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_trustmrr_search

Search public startups with payment-provider-verified revenue and MRR. Filter by category, country, provider, growth, price, and for-sale status.

Instructions

Search the TrustMRR dataset. Searches public startups with payment-provider-verified revenue and MRR, stored in a search index. Filter by category, country, payment provider, target audience, tech, marketing channel, listing tier and for-sale status, and by revenue/MRR/traffic/growth/multiple/asking-price ranges. Sort enum: relevance, mrr_desc, revenue_desc, revenue_30d_desc, traffic_desc, growth_desc, deal_score_desc, price_asc, price_desc, multiple_asc, founded_desc. status enum: active, removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name, description, seller message and business summary, max 256 characters
pageNoPage number, defaults to 1
slugNoExact startup slug filter, max 128 characters
sortNoSort enum: relevance, mrr_desc, revenue_desc, revenue_30d_desc, traffic_desc, growth_desc, deal_score_desc, price_asc, price_desc, multiple_asc, founded_desc
techNoDetected tech-stack slug filter (e.g. nextjs, reactnative), max 128 characters
statusNoLifecycle enum: active, removed
channelNoDetected marketing-channel slug filter (e.g. meta-ads, seo), max 128 characters
countryNoExact ISO country-code filter (e.g. US), max 128 characters
max_mrrNoMaximum verified MRR in USD
min_mrrNoMinimum verified MRR in USD
on_saleNoFilter for startups currently listed for sale
categoryNoExact category filter (e.g. SaaS, Artificial Intelligence, Mobile Apps), max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
min_growthNoMinimum 30-day revenue growth percentage
min_revenueNoMinimum verified all-time revenue in USD
min_trafficNoMinimum last-30-days traffic (visits)
is_sponsoredNoFilter for sponsored (paid-placement) listings
listing_tierNoFor-sale listing-tier filter (e.g. pro), max 128 characters
max_multipleNoMaximum asking-price-to-revenue multiple
business_typeNoBusiness-type filter (e.g. B2B, B2C), max 128 characters
min_ahrefs_drNoMinimum Ahrefs Domain Rating
min_revenue_30dNoMinimum verified last-30-days revenue in USD
target_audienceNoTarget-audience filter (e.g. B2B, B2C), max 128 characters
max_asking_priceNoMaximum asking price in USD
min_asking_priceNoMinimum asking price in USD
payment_providerNoPayment-provider filter (e.g. stripe, revenuecat, superwall, creem), max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "mrr_desc",
+  "revenue_desc",
+  "revenue_30d_desc",
+  "traffic_desc",
+  "growth_desc",
+  "deal_score_desc",
+  "price_asc",
+  "price_desc",
+  "multiple_asc",
+  "founded_desc"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "active",
+  "removed"
+]
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that the tool searches a public, verified dataset and lists filterable dimensions, but it does not state response format, pagination behavior, default sorting, or whether filters are combined. The non-destructive nature is implied by 'Searches' but not explicitly confirmed.

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 three sentences, front-loaded with the tool's purpose, and reasonably compact for a 26-parameter tool. However, it repeats the full sort enum and status enum that already exist in the schema, which is redundant structured data. It earns a 4 for structure and brevity, with minor redundancy.

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 complex 26-parameter search tool with no output schema and no annotations, the description is incomplete: it never states what the response contains, whether filters are ANDed, what the default sort is, or pagination behavior beyond the schema's page_size note. It does clarify the dataset scope and available filters, which is substantial, but the missing return-value and default-behavior information leaves gaps.

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 26 parameters with descriptions. The description adds a high-level grouping of filter categories and repeats the sort/status enums, but does not clarify parameter semantics beyond the schema. The baseline of 3 is appropriate since the schema carries the heavy lifting.

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 states a specific verb ('Search') and resource ('the TrustMRR dataset', 'public startups with payment-provider-verified revenue and MRR'), making the core function clear. It does not explicitly name or differentiate sibling search/facet/item tools, though mentioning 'search index' hints at its role. This is clear but lacks explicit sibling differentiation.

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?

The description implies usage: use this tool when searching or filtering the TrustMRR dataset, and it enumerates many filter dimensions. It provides no explicit guidance on when to prefer alternatives like datasets_trustmrr_facets, datasets_trustmrr_item, or trustmrr_startup, nor any exclusions. This is implied usage only.

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