Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_trustmrr_search

Search startups with payment-provider-verified revenue and MRR. Filter by category, country, payment provider, revenue range, and other criteria.

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

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as read-only nature, pagination behavior, rate limits, or what happens on failure. Only states it searches public startups.

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?

Two sentences plus enumeration of sort and status. Front-loaded but redundant with schema. Could be more structured and concise by avoiding repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema. Description does not explain what the search results contain (e.g., key fields of startups) or mention pagination/result count. For a tool with many optional filters, more context is needed.

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 has 100% description coverage for all 26 parameters. Description adds a high-level summary of filter types but does not provide deeper semantics beyond what schema already offers. Baseline 3 due to high coverage.

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?

Clearly states it searches the TrustMRR dataset of public startups with verified revenue. Mentions filtering categories. Distinguishes from siblings by naming the specific dataset, but does not contrast with similar search tools like datasets_trustmrr_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?

Implied usage as primary search tool for TrustMRR data. No explicit guidance on when to use this versus alternatives like datasets_trustmrr_item or datasets_trustmrr_facets.

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