There's An AI For That

Search fundraises

search_fundraises

Read-only

Search and list public AI company fundraising rounds. Filter by company name, round type, announcement date, or participating investor slug, and sort by announcement date.

Input Schema

Name	Required	Description	Default
`sort`	No	Field used to sort results.	announced_date
`limit`	No
`order`	No	Sort direction. Use desc for the latest fundraises first.	desc
`query`	No	Optional company name or round type. Omit it, pass an empty string, or pass "*" to search all public fundraising rounds.
`since`	No	Include rounds announced on or after this date (YYYY-MM-DD).
`until`	No	Include rounds announced on or before this date (YYYY-MM-DD).
`investor`	No	Optional verified active investor slug returned by search_investors.
`round_type`	No	Exact fundraising round type to include, such as Seed or Series A.

Output Schema

Name	Required	Description	Default
`fundraises`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 13, 2026

addedInput schema / properties / investor

Added value: +{
+  "description": "Optional verified active investor slug returned by search_investors.",
+  "type": "string"
+}

addedInput schema / properties / order

Added value: +{
+  "default": "desc",
+  "description": "Sort direction. Use desc for the latest fundraises first.",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Company name associated with a fundraising round."New value: +"Optional company name or round type. Omit it, pass an empty string, or pass \"*\" to search all public fundraising rounds."

addedInput schema / properties / round_type

Added value: +{
+  "description": "Exact fundraising round type to include, such as Seed or Series A.",
+  "enum": [
+    "Pre-Seed",
+    "Seed",
+    "Series A",
+    "Series B",
+    "Series C",
+    "Series D",
+    "Series E",
+    "Series E+",
+    "Series F",
+    "Series G",
+    "Bridge",
+    "Convertible Note",
+    "SAFE",
+    "Pre-IPO",
+    "IPO",
+    "Debt Financing",
+    "Growth Round"
+  ],
+  "type": "string"
+}

addedInput schema / properties / since

Added value: +{
+  "description": "Include rounds announced on or after this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "default": "announced_date",
+  "description": "Field used to sort results.",
+  "enum": [
+    "announced_date"
+  ],
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Include rounds announced on or before this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[]

addedOutput schema / properties / fundraises / items / properties / amount_raised
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / fundraises / items / properties / announced_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / fundraises / items / properties / company_slug
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / fundraises / items / properties / currency
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / fundraises / items / properties / round_type
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / fundraises / items / required

Previous value: -[
-  "id",
-  "entity_type",
-  "name",
-  "slug",
-  "url"
-]New value: +[
+  "id",
+  "entity_type",
+  "name",
+  "slug",
+  "url",
+  "announced_date",
+  "amount_raised",
+  "currency",
+  "round_type",
+  "company_slug"
+]

AddedSep 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful scope context ('public AI company' rounds) but says nothing about result volume, default page size behavior, or pagination, so it adds only modest value beyond 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.

Conciseness4/5

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

Two compact clauses, front-loaded with the verb and resource, followed by the filtering and sorting capabilities. No filler sentences, though the sorting note is mildly redundant with the schema's sort/order parameters.

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?

An output schema exists so return values need not be described, and annotations carry the safety profile. With 88% schema coverage across 8 optional parameters, the description's coverage of scope and filters is adequate; only the lack of sibling routing guidance keeps it from being fully complete.

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 88%, so the schema already documents every parameter including the wildcard/empty-string behavior for query and the enum values. The description restates the filterable dimensions (company name, round type, date, investor slug) without adding format, matching, or precedence semantics beyond what the schema provides.

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/list) and resource (public AI company fundraising rounds), which cleanly separates it from the singular get_fundraise and from search_deals. It enumerates filterable dimensions, but never names the sibling tools it competes with, so differentiation relies on the agent knowing the sibling set.

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 by listing available filters, but gives no explicit when-to-use versus get_fundraise or search_deals, and no exclusions. The only cross-tool hint ('investor slug returned by search_investors') lives in the schema, not the description, so the routing guidance is implicit rather than stated.

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

All There's An AI For That 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.