fundz

Search Raised & Hiring

search_raised_and_hiring

Read-onlyIdempotent

Raised & Hiring, the same list as app.fundz.net/funded-and-hiring: companies with a verified funding round in the last 12 months that have open job postings now, scored and refreshed daily, with the latest round, open postings and exec hires in the last 90 days, and hiring signals. Every company listed has at least one open posting; an exec hire alone does not qualify. Filter by US state, funding series, company name, company size, the role they are hiring (title_family, keyword, department) or new this week. Page through every match with page; use since to get only companies that joined the list on or after a date. To find companies hiring a leadership role, USE title_family (for example title_family "sales_leadership" for "hiring a VP Sales, Head of Sales, Sales Director or CRO"), never a single keyword: titles vary ("VP Sales" returns nothing at a company that posts "Director of Sales"). keyword also takes several titles joined with " OR " or "|". department "Sales" also covers Go-to-market, GTM, Revenue and Business Development.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more.
`sort`	No	score (default), funding_date (latest round first) or newest (most recently added first)
`limit`	No	Results per page (default 20, max 50)
`since`	No	Only companies that joined the list on or after this ISO date, e.g. "2026-10-01" (sorts newest first)
`state`	No	US state name or 2-letter code, comma-separated for several, e.g. "Texas, CO"
`series`	No	Latest funding series, comma-separated, e.g. "Seed, Series A"
`keyword`	No	Only companies with an open posting whose title contains this. Several: "Director of Sales OR Head of Sales".
`new_only`	No	Only companies that joined the list in the last 7 days
`department`	No	Only companies with an open posting in this department. "Sales" also matches Go-to-market, GTM, Revenue, Commercial and Business Development.
`company_name`	No	Company name (partial, case-insensitive)
`my_territory`	No	Only companies inside the locations of the user's saved filters
`title_family`	No	Title family: one OR set of roles, comma-separated for several. sales_leadership = VP / Vice President / Head of / Director of Sales, Revenue or GTM, plus CRO and Chief Revenue Officer. sales_manager = Sales Manager titles (add it when the user says "sales leaders and managers"). marketing_leadership, engineering_leadership, finance_leadership.
`employees_max`	No	Maximum employee count (same handling of unknown headcount)
`employees_min`	No	Minimum employee count. Companies with no headcount on file are kept, marked "headcount unknown" and ranked after the known in-range ones.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 12, 2026

addedInput schema / properties / department

Added value: +{
+  "description": "Only companies with an open posting in this department. \"Sales\" also matches Go-to-market, GTM, Revenue, Commercial and Business Development.",
+  "type": "string"
+}

addedInput schema / properties / employees_max

Added value: +{
+  "description": "Maximum employee count (same handling of unknown headcount)",
+  "type": "number"
+}

addedInput schema / properties / employees_min

Added value: +{
+  "description": "Minimum employee count. Companies with no headcount on file are kept, marked \"headcount unknown\" and ranked after the known in-range ones.",
+  "type": "number"
+}

addedInput schema / properties / keyword

Added value: +{
+  "description": "Only companies with an open posting whose title contains this. Several: \"Director of Sales OR Head of Sales\".",
+  "type": "string"
+}

addedInput schema / properties / title_family

Added value: +{
+  "description": "Title family: one OR set of roles, comma-separated for several. sales_leadership = VP / Vice President / Head of / Director of Sales, Revenue or GTM, plus CRO and Chief Revenue Officer. sales_manager = Sales Manager titles (add it when the user says \"sales leaders and managers\"). marketing_leadership, engineering_leadership, finance_leadership.",
+  "type": "string"
+}

AddedOct 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real behavioral context beyond that: daily refresh cadence, the 'at least one open posting' qualification rule, and the 90-day window for round/postings/exec-hire signals. No auth or rate-limit detail, but the freshness and inclusion semantics are valuable.

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 what the list is before the filtering mechanics, and every sentence carries information. It is dense and a few items (department expansion, keyword OR syntax) are repeated verbatim from the schema, which is mild redundancy rather than waste.

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 14-parameter, no-required, no-output-schema tool this covers the essentials: list definition, refresh cadence, inclusion rules, pagination ('the reply ends with the total and next_page'), and filter guidance. Auth/permission expectations and rate limits are unstated, which is the main remaining gap.

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, but the description adds reasoning the schema does not: why title_family beats keyword, that keyword accepts multiple titles joined with OR or '|', and that department 'Sales' also covers Go-to-market/GTM/Revenue/Business Development. These are genuine semantic aids rather than restatements, though some of it duplicates the schema text.

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 with exact scope: companies with a verified funding round in the last 12 months that also have open postings, scored and refreshed daily. The qualification rule ('an exec hire alone does not qualify') makes it cleanly distinguishable from search_hiring_intel and search_funding_rounds, which cover only one half of the intersection.

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?

Gives strong in-tool guidance: use title_family rather than a single keyword for leadership roles, and explains why ('VP Sales' returns nothing at a company posting 'Director of Sales'). It also documents department expansion and the OR syntax. It stops short of naming when to prefer a sibling tool (e.g. pure funding or hiring searches), so it lacks explicit alternatives.

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

All fundz 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.

Resources

Need Help?