Skip to main content
Glama
Sign In

StartupHub.ai

by ai.startuphub
OverviewDiscussionsAdmin

Search new domains

search_domains
Read-only

Domain radar: newly registered names from our discovery queue (NRD, registries, GitHub orgs). This is NOT a company profile. Returns apex, registration date, registrar, mailbox signal, quality score, and status (queued / quality_failed). startup_slug is set only after we promote a real homepage into the directory. Always sorted newest first (created_at desc). Use search_startups for companies. Pro Lite and higher. 1 db credit. Needs a free StartupHub.ai account.

Input Schema

NameRequiredDescriptionDefault
qNoSubstring match on apex or candidate name. Needs at least 2 characters after removing % _ and commas, otherwise no filter.
tldNoComma-separated TLDs, e.g. 'ai,io'. Only ai, io, xyz, so, com and security filter anything; other values apply no filter. Maps to the NRD/CT sources and combines with source by OR.
apexNoExact hostname lookup, e.g. acme.ai. A leading www. is stripped; a value with no dot returns 400 invalid_apex. Overrides q.
limitNo1-100.
offsetNoSkip this many rows, for paging.
sourceNoComma-separated raw source or bucket ids, e.g. 'dot_ai_nrd', 'dot_ai_zone', 'github_new_org', 'uk_companies_house'.
statusNoComma-separated: queued, quality_failed, promoted, rejected. Default is queued,quality_failed.
promotedNo'true' = only names that already have a public startup profile.
is_parkedNoDomain is parked.
created_afterNoISO date. Rows we first ingested on or after this time.
created_beforeNoISO date. Rows we first ingested on or before this time.
has_real_emailNoMailbox on the domain (MX is not empty).
has_real_contentNoLast homepage probe found real body copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / apex / description
      Previous value: -"Exact hostname lookup, e.g. acme.ai"New value: +"Exact hostname lookup, e.g. acme.ai. A leading www. is stripped; a value with no dot returns 400 invalid_apex. Overrides q."
    • addedInput schema / properties / created_before
      Added value: +{
+  "description": "ISO date. Rows we first ingested on or before this time.",
+  "type": "string"
+}
    • addedInput schema / properties / has_real_content / description
      Added value: +"Last homepage probe found real body copy."
    • addedInput schema / properties / is_parked
      Added value: +{
+  "description": "Domain is parked.",
+  "enum": [
+    "true",
+    "false"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / limit / description
      Added value: +"1-100."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many rows, for paging.",
+  "type": "number"
+}
    • changedInput schema / properties / q / description
      Previous value: -"Substring match on apex or candidate name."New value: +"Substring match on apex or candidate name. Needs at least 2 characters after removing % _ and commas, otherwise no filter."
    • changedInput schema / properties / source / description
      Previous value: -"Raw source or bucket id, e.g. 'dot_ai_nrd' or 'dot_ai_zone'."New value: +"Comma-separated raw source or bucket ids, e.g. 'dot_ai_nrd', 'dot_ai_zone', 'github_new_org', 'uk_companies_house'."
    • changedInput schema / properties / status / description
      Previous value: -"queued, quality_failed, promoted, rejected. Default is queued,quality_failed."New value: +"Comma-separated: queued, quality_failed, promoted, rejected. Default is queued,quality_failed."
    • changedInput schema / properties / tld / description
      Previous value: -"Comma-separated TLDs, e.g. 'ai,io'. Maps to the NRD/CT sources."New value: +"Comma-separated TLDs, e.g. 'ai,io'. Only ai, io, xyz, so, com and security filter anything; other values apply no filter. Maps to the NRD/CT sources and combines with source by OR."
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description does add value beyond that — credit cost, tier/account prerequisites, and the newest-first sort order — but it stops short of the richer behavioral detail (pagination interaction with offset, rate limits) that a 4-5 would need.

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?

Front-loaded with the core identity ('Domain radar...') before routing, sorting, and entitlement notes. Nine short clauses for a 13-parameter tool is proportionate, though a couple of the entitlement sentences could be tightened.

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

Completeness5/5

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

With 13 parameters, no output schema, and no required fields, the description compensates well: it enumerates the returned fields (apex, registration date, registrar, mailbox signal, quality score, status), documents the sort order, states what startup_slug means, and covers cost and access requirements. Nothing critical for correct invocation is missing.

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% and there is no output schema, so the schema itself carries the per-parameter semantics (q substring rules, tld OR behavior, apex override, status default). The description only restates status values and source origin types at a high level, adding little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'newly registered names from our discovery queue (NRD, registries, GitHub orgs)' and explicitly negates the likely confusion with 'This is NOT a company profile.' An agent can distinguish it from search_startups without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use search_startups for companies' paired with the 'NOT a company profile' exclusion. It also discloses the gating conditions (Pro Lite and higher, 1 db credit, free account required), so an agent knows both when to select it and whether it can call it.

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

All StartupHub.ai toolsInspect
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.

Resources