HirePulse MCP is a B2B company-research server that turns a domain into public technology, hiring, advertising, and contact signals, with free sandbox calls and paid x402/USDC lookups.
Tech stack lookup: detect pixels, analytics, CMS, e-commerce, hosting, payments, and email/DNS (SPF, DMARC) from a website.
Open jobs & hiring intent: pull live job-board postings (Greenhouse, Lever, Ashby, Workable, etc.) and score buying intent 0–100 with function and technology breakdowns.
Google Ads transparency: see whether a domain advertises, with ad formats, dates, previews, and region filters.
Combined company profile / footprint check: run tech, hiring, and ads in parallel for due-diligence style research.
Batch & prioritization: bulk lookup across up to 50 domains and find_hot_buyers to rank 2–25 domains by hiring intent.
Contacts & content: extract published emails/social links and convert web pages to LLM-ready Markdown.
Commerce & merchant trust: pre-purchase merchant checks, x402 merchant scanning, promo-code finding, product-URL-to-JSON, vendor stability scoring, store readiness audits, lead finding, and signed merchant badges.
Privacy & guidance: private_blind_lookup for blind execution and a free advisor tool that recommends the right tool, cost, and request.
Access model: free sandbox domains (example.com, linear.app, stripe.com, shopify.com), 5 free calls/day per IP, 25-call trial, then pay-per-result via x402.
Provides a Google Ads transparency tool for investigating companies' advertising activity as part of HirePulse company screening.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@HirePulse MCP what's the tech stack and hiring intent for stripe.com?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Research a company from public technology, open jobs and hiring signals, Google Ads and published contacts. A combined profile costs $0.03 per qualifying result and includes breakout_summary growth estimates. Start with a labeled free sandbox, then use a 25-call trial for real research. Growth signals are not financial forecasts.
Start here: research one company in three steps — connect the 8-tool B2B profile, try a labeled free demo, then research a real domain.
No npm package is needed for clients that support remote HTTP MCP:
{
"mcpServers": {
"hirepulse": {
"url": "https://gethirepulse.xyz/mcp?profile=b2b&ref=github"
}
}
}Claude Code:
claude mcp add --transport http hirepulse 'https://gethirepulse.xyz/mcp?profile=b2b&ref=github'Clients requiring stdio can bridge the remote endpoint:
{
"mcpServers": {
"hirepulse": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://gethirepulse.xyz/mcp?profile=b2b&ref=github"]
}
}
}Related MCP server: llmsproxy
hirepulse-mcp@1.0.0 is published and verified against all 26 live tools, including claim_free_trial. Requires Node.js 20+.
{
"mcpServers": {
"hirepulse": {
"command": "npx",
"args": ["-y", "hirepulse-mcp@1.0.0"]
}
}
}The npm proxy exposes the full 26-tool gateway. For a focused 8-tool or 11-tool setup, use the remote profiles above. Source development: npm ci, npm run build, npm test.
curl -X POST 'https://gethirepulse.xyz/v1/company-profile?ref=github' \
-H 'Content-Type: application/json' \
-d '{"domain":"example.com"}'example.com returns explicitly labeled synthetic sandbox data, not a live company result, and does not consume the shared free allowance.
For real company lookups, claim_free_trial / POST /v1/trial grants an eligible business email or active Base wallet a one-time 25-call pass valid for 30 days. No email is sent. Keep the returned token private; send it using X-Trial-Token or MCP params._meta["hirepulse/trial_token"]. Private lookup and paid inbox allocation are excluded.
Guided setup and demo · Investor radar n8n workflow · API catalog
Commerce research: https://gethirepulse.xyz/mcp?profile=commerce&ref=github (11 tools).
Complete v12 catalog: https://gethirepulse.xyz/mcp?ref=github (26 tools; existing clients remain supported).
Versioned machine-readable configurations: B2B, Commerce, and complete catalog.
The proxy forwards the live gateway catalog: 26 canonical MCP tools in version 12
(verified 26 October 2026). The legacy names 00_ask_hirepulse_advisor and
verify_domain_legitimacy_and_security remain callable for compatibility but
are omitted from tools/list. Schemas are forwarded from the gateway rather
than maintained in a second copy. Every input parameter has a description.
Tools cover website technology,
public job boards, hiring signals, Google Ads transparency, company profiles,
contacts, web-to-Markdown, merchant screening and commerce evidence.
Five successful free calls per UTC day per IP are shared across tools.
Batch and hot-buyer scans have separate limits and a two-step quote flow.
Empty results are not charged. Paid results use x402, USDC on Base:
see the live catalog for each price; hot buyers cost $0.25 per hot company.
Use pre_purchase_merchant_trust_check for an online shop before buying goods.
Use x402_merchant_trust_check instead for an x402 API before signing a crypto
payment. Neither scan certifies safety or authorizes spending. For
private_blind_lookup, arguments contains only tool and target; select the
bundle tier in MCP request metadata params._meta["hirepulse/private-tier"],
outside arguments, or with the HTTP X-Private-Query-Tier: bundle header.
Node.js 20 or newer
Network access to https://gethirepulse.xyz
If your client supports remote HTTP MCP directly, you can connect to
https://gethirepulse.xyz/mcp without this package. Use this stdio proxy
when your client (such as Claude Desktop) only supports local stdio MCP servers.
Calls targeting linear.app, stripe.com, shopify.com, and example.com
are free on the remote gateway so you can test tool calling end-to-end
without an x402 wallet.
MIT
Returns structured public evidence and explicit unknowns. Compares a brand with up to 3 competitors as shopping schema: prices, ratings, availability, shipping and returns, from one sampled product per store. $0.02 per comparison. Use for a bounded cross-store comparison; use universal_product_url_to_json for one product or muse_agentic_store_readiness_auditor for a single-store discovery audit. Unavailable evidence stays unknown.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| competitor_domains | Yes | One to three distinct bare public competitor store domains to compare against domain; one product is sampled per store. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavioral context the annotations cannot convey: a $0.02 per-comparison cost, that only one product is sampled per store (a representativeness caveat), and that missing evidence is returned as unknown rather than fabricated. It doesn't discuss latency or failure/refund behavior on failed comparisons, which keeps it off a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four tight sentences with no filler; the evidence dimensions and pricing are front-loaded before the routing guidance. The opening 'Returns structured public evidence and explicit unknowns' is slightly abstract compared to the concrete sentence that follows it, but nothing is wasted overall.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and all three parameters documented, the description only needs to frame scope, cost, and alternatives — which it does. The sampling caveat and unknown-handling rule cover the main interpretive risks. Minor gap: no guidance on what happens if a domain is unreachable or whether the $0.02 is still charged, which matters for a paid tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already explains that domains must be bare public domains and that competitor_domains takes one to three distinct entries. The description restates the up-to-3 limit and sampling behavior but adds no syntax, normalization, or validation detail beyond the schema. Baseline 3 applies when structured fields do the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (compares), a bounded resource set (a brand vs up to 3 competitors), and the exact evidence dimensions covered: prices, ratings, availability, shipping and returns. The 'one sampled product per store' clause defines the unit of analysis, so an agent knows precisely what output granularity to expect.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use for a bounded cross-store comparison' and names two alternatives with the condition that selects each: universal_product_url_to_json for a single product, muse_agentic_store_readiness_auditor for a single-store discovery audit. This is textbook when-to-use/when-not-to-use routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Free advisor that maps a goal (B2B leads, hiring signals, buying intent, tech stack, Google Ads, due diligence) to the matching HirePulse tool, its price, the free-call balance and a ready-to-run request. Use when the right tool or expected cost is unclear; go directly to get_company_profile for a known domain and a full company brief. The returned request is a preview and is not executed by this advisor.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_goal | Yes | Describe the research goal so the advisor can recommend a tool and estimate its list price. | |
| budget_usd | No | Optional USD budget used for recommendations only; this does not authorize spending or payment. | |
| domain_count | No | Number of companies you plan to research, used for batch sizing and cost estimates. | |
| sample_domain | No | Optional bare public company domain for a concrete request example and existing cached hints; no new lookup is run. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial behavioral fact that the returned request is a preview and is not executed, plus that the advisor is free and that sample_domain draws on cached hints without running a new lookup. Those are exactly the traits an agent needs to avoid assuming a side effect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the capability, then the routing rule, then the non-execution caveat. Every sentence carries distinct information with no repetition of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shape need not be explained; the description covers what is returned conceptually (tool, price, balance, request preview). With annotations, full schema coverage, and only one required parameter, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and all four parameters are documented there, so the baseline is 3. The description reinforces the intent (goal → tool + price estimate) but adds no format, syntax, or range detail beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — a free advisor that maps a stated goal to the matching HirePulse tool along with price, free-call balance, and a ready-to-run request — and enumerates the goal categories it handles. It explicitly separates itself from the sibling get_company_profile, so an agent can pick between them without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit use condition ("when the right tool or expected cost is unclear") and an explicit alternative with its own condition ("go directly to get_company_profile for a known domain and a full company brief"). Nothing is left to inference about routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Assess a B2B vendor before procurement using public technology and hiring evidence; returns a stability assessment, evidence gaps and limitations. Use for supplier due diligence; use get_company_profile for general company enrichment or pre_purchase_merchant_trust_check for an online shop purchase. Missing history stays unknown, never an invented trend. $0.10 only when a useful assessment is returned.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| vendor_domain | Yes | Public domain without scheme, path or port. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real behavioral context: absent history is reported as unknown rather than inferred, and billing is conditional ('$0.10 only when a useful assessment is returned'). It stops short of describing latency, rate limits, or what evidence sources are actually consulted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the return contract and keeps the routing guidance tight. There is mild redundancy between 'Returns structured public evidence and explicit unknowns' and the later 'returns a stability assessment, evidence gaps and limitations', which restates the same idea.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be explained, and the description still covers scope, uncertainty handling, cost, and sibling routing. What remains thin is the evidence base itself (which public signals count as technology/hiring evidence), which would help an agent judge applicability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for both parameters, including the domain format constraint and the opt-in context field, so the schema carries the parameter burden. The description adds nothing about parameter values beyond the implicit notion of a vendor domain, which is the correct baseline here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Assess a B2B vendor before procurement using public technology and hiring evidence') and names the artifact returned ('a stability assessment, evidence gaps and limitations'). It is explicitly differentiated from get_company_profile and pre_purchase_merchant_trust_check, so an agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear use condition ('supplier due diligence') and names two alternatives with the situations that select them (general enrichment, online-shop purchase). The exclusions are concrete rather than implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Runs one tool (tech stack, open jobs, hiring intent, Google Ads or company profile) on up to 50 domains. Step 1 is a free check that returns a quote_id priced only for rows with data; step 2 pays that exact amount, at most $1.00. Rows without data are free. Use for the same lookup across several known domains; use get_company_profile for one domain or find_hot_buyers to rank hiring signals. A quote does not authorize payment.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | Data tool to run for each domain during quote creation; omit when redeeming a quote_id. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| domains | No | Public company domains without a URL scheme, path or port. | |
| quote_id | No | quote_id from step 1. Send it alone to pay and receive the results. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says step 2 'pays that exact amount' and that 'A quote does not authorize payment,' which describes a monetary transaction. This directly contradicts the readOnlyHint=true annotation, which asserts the tool has no side effects. Despite otherwise useful disclosure about free checks and pricing caps, the contradiction is a critical inconsistency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core action and domain limit, then follows with pricing details and alternatives in a logical sequence. Every sentence adds distinct information without redundancy, and the closing warning about quotes is a useful reminder.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists (so return values need not be explained) and the annotations (readOnlyHint, openWorldHint), the description covers all necessary aspects for correct invocation: tool selection, domain limits, the two-step quote/payment process, pricing rules, and explicit alternatives. Nothing essential for calling the tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameter meanings are fully documented in the input schema (e.g., tool enum, domains format, quote_id usage). The description adds context about the two-step flow and the 'at most $1.00' price cap, but does not meaningfully extend the semantic definition of any parameter beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action (runs one tool on up to 50 domains) and enumerates the available tools, making the scope immediately clear. It also explicitly names sibling tools for alternative use cases, so an agent can distinguish this tool from get_company_profile and find_hot_buyers without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It specifies when to use this tool (same lookup across several known domains) and names two explicit alternatives with their respective conditions (get_company_profile for one domain, find_hot_buyers for ranking hiring signals). The two-step quote/payment flow is also clearly described as part of the usage pattern.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Coupon code candidates published in the homepage metadata of a shop, with the source text. Codes are not verified at checkout. $0.01 per non-empty result. Use to collect possible discounts before checkout; use universal_product_url_to_json for product prices and availability. Does not apply coupons or place an order.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| product_category | No | Optional category context for the supplied store; does not guarantee category-specific or checkout-verified coupons. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly and openWorld, but the description adds substantive context beyond them: unverified-at-checkout caveat, source-text provenance, explicit unknowns, a $0.01 per non-empty result pricing model, and confirmation it does not mutate anything. These are exactly the traits an agent needs for cost/risk judgment.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Every sentence earns its place: return type, provenance, verification caveat, pricing, usage routing, and exclusions. Slightly abstract opener ('structured public evidence and explicit unknowns') precedes the concrete statement, so it is not perfectly front-loaded but remains tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema available, the description need not explain return structure; it fills the remaining gaps an agent needs — provenance, non-verification, cost, and non-mutation — making the definition complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the domain/context/product_category semantics are already fully documented in the schema. The description adds no syntax or format detail beyond it, which matches the baseline 3 when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: returns coupon code candidates published in a shop's homepage metadata, along with source text. It explicitly distinguishes itself from the sibling universal_product_url_to_json and clarifies that codes are not checkout-verified, so the agent can tell what kind of artifact it gets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Names the use case ('collect possible discounts before checkout'), the alternative for a different need (universal_product_url_to_json for prices and availability), and the exclusions ('does not apply coupons or place an order'). Both when-to-use and when-not-to-use are explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get a one-time trial pass: 25 free successful calls of any single tool, not tied to your IP, valid 30 days. Send exactly one of: a Base wallet that has activity, or a work email (no email is sent). Then pass the token as params._meta["hirepulse/trial_token"] or the X-Trial-Token header.
| Name | Required | Description | Default |
|---|---|---|---|
| No | A work email address; free mailbox providers are not accepted. | ||
| wallet | No | A Base address with at least one transaction or $0.10 USDC. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations, it discloses the key behavioral traits an agent needs: one-time use, 25 successful calls, any single tool, not tied to IP, valid 30 days, and where to place the returned token. The readOnlyHint=false annotation is consistent with a claim action, and the description adds substantial operational context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences, front-loaded with the core offer, followed by the input rule and token-passing mechanics. Every sentence carries actionable information with no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter claim tool with no output schema, the description covers what the trial provides, the mutually exclusive input rule, and how to use the token afterward. Nothing essential for calling it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds a constraint not expressed in the schema: submit exactly one of email or wallet. It also clarifies that no email is sent and how the resulting token is passed via params._meta or the X-Trial-Token header, which is valuable semantic guidance beyond the field descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a precise verb and resource: claim a one-time trial pass of 25 free successful calls. It specifies scope (any single tool), duration (30 days), and non-IP binding, so an agent can tell exactly what the tool offers without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear usage condition (claim a one-time trial) and an explicit input constraint: send exactly one of a Base wallet or a work email. It does not name when not to call it or any alternative path, but there is no obvious sibling alternative among the listed tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Public operating footprint of a company for due diligence and vendor risk: ad and analytics tags, an active job board and Google Ads, each marked found, not_found or unknown. Facts only, no financial estimates. $0.03, charged only when two of the three checks return data. Use for found/not_found operating evidence; use get_company_profile for published contacts and breakout_summary growth signals, or b2b_vendor_stability_evaluator for a procurement assessment.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public company domain without a URL scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint and openWorldHint; the description adds the material behavioral facts not covered there: the $0.03 cost, that billing only triggers when two of three checks return data, that results are marked found/not_found/unknown, and a scope limit ("Facts only, no financial estimates"). It does not discuss latency or rate limits, so not a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: capability and output encoding first, scope limit second, sibling routing last. Every clause carries information an agent needs; nothing is redundant with structured fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists so return values needn't be re-explained, and the description still notes the three result states. Cost, billing trigger, scope limits, and alternatives are all covered. Only missing element is what happens when checks are "unknown" / partial-failure reporting detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters are documented in the schema, including the domain format constraint and the purpose of the optional context field. The description adds no syntax or format detail beyond what the schema already provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource ("public operating footprint of a company") and enumerates exactly what is checked: ad/analytics tags, active job board, Google Ads. An agent can immediately tell it apart from get_company_profile or get_company_open_jobs, which cover narrower slices.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly names the use case ("Use for found/not_found operating evidence") and routes to two named alternatives with the condition that selects each: get_company_profile for contacts/growth signals, b2b_vendor_stability_evaluator for procurement assessment. Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Allocate an inbox for authorized inbound testing. x402: $0.01 per started 600 seconds, TTL 60–3600 seconds; default $0.01 for 600 seconds. No free company-tool trial applies. No account/key setup: payment result returns an inbox-scoped access_token and capability. Reuse idempotency_key on retries. Reads, code polling, deletion and up to 50 messages included; SMTP delivery/valid OTP are not guaranteed.
| Name | Required | Description | Default |
|---|---|---|---|
| ttl_seconds | No | ttl_seconds parameter for create_email_inbox | |
| idempotency_key | Yes | idempotency_key parameter for create_email_inbox |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) by disclosing the pricing meter ($0.01 per started 600 seconds), TTL bounds, the fact that a payment result returns an inbox-scoped access_token and capability instead of requiring account setup, idempotency-on-retry behavior, and explicit non-guarantees (SMTP delivery, valid OTP). This is exactly the operational context an agent needs before spending money.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose, then pricing, then auth/idempotency, then included features and caveats – a sensible order with no filler. It is dense and jargon-heavy ('x402', 'capability') at the cost of a little readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a paid, mutating allocation tool with an output schema, the description covers cost, TTL, credential return, retry safety, and feature boundaries. An agent could decide whether to call it and how to retry correctly without consulting anything else.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3; the description still adds value by tying ttl_seconds to a billing unit ('per started 600 seconds', default $0.01 for 600s) and by explaining the retry semantics of idempotency_key rather than just its pattern. The 60–3600 range is redundant with the schema's min/max.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource – 'Allocate an inbox' – with the intended scope ('authorized inbound testing'). This immediately distinguishes it from the sibling lifecycle tools list_email_messages, get_email_code, and delete_email_inbox.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clear context for use ('authorized inbound testing', no account/key setup required) and a note that reads, code polling and deletion are included in the allocation. It never explicitly names alternatives or exclusions, such as when to prefer claim_free_trial or which sibling consumes the returned token, but the operating context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Delete your existing inbox and revoke access to its mailbox content. Use after testing is complete; this operation does not read messages or extract codes. Pass inbox_id, capability and access_token from create_email_inbox. No additional charge or new payment. Deletion is destructive: read needed messages before deleting.
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | inbox_id parameter for delete_email_inbox | |
| capability | Yes | capability parameter for delete_email_inbox | |
| access_token | No | Use the scoped access_token returned by create_email_inbox. Optional only for an existing provisioned private pilot connection. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the destructiveHint annotation, the description explains that deletion revokes mailbox access, does not read messages or extract codes, incurs no additional charge, and should be preceded by reading needed messages. These are concrete behavioral consequences that help an agent act safely.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four compact sentences and front-loads the action and scope. Each sentence adds a distinct operational detail, including the deletion warning and parameter source.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The definition is complete for a destructive deletion tool: annotations declare destructiveness, the schema fully covers parameters, an output schema exists, and the description adds timing, source, and safety guidance. Nothing essential is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 the three parameters. The description adds useful provenance by saying inbox_id, capability, and access_token should come from create_email_inbox, though it does not clarify that access_token is optional in some existing-connection cases.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: delete an existing inbox and revoke access to its mailbox content. It also distinguishes the operation from reading messages or extracting codes, so an agent can tell it apart from list_email_messages and get_email_code.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear usage condition: use after testing is complete, and read needed messages before deleting. It also says the operation does not read messages or extract codes, which implicitly points to the read/extract siblings, but it does not explicitly name them as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Website tech stack for a company domain: ad pixels (Meta, Google Ads, LinkedIn, TikTok), analytics, tag managers, CMS, e-commerce, hosting and payments, plus email provider, SPF and DMARC from DNS. $0.005 per result after 5 free calls a day; blocked or empty sites are free. Use for technology-only research; use get_company_profile when hiring, ads and contacts are also needed.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without a URL scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the cost model ($0.005 per result after 5 free calls a day), that blocked or empty sites are free, and that email/SPF/DMARC come from DNS rather than page scraping. These are decision-relevant facts an agent cannot get from 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: the first front-loads what is returned, the second handles cost and sibling routing. No filler, no repetition of the title, and the ordering puts the payload description before the caveats.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, so return values need not be explained; coverage of categories in the description plus pricing and the no-result-free policy covers what an agent needs to call it responsibly. Nothing material is missing for a read-only, single-required-param lookup.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the domain format constraint ('without a URL scheme, path or port') and the context field are already fully documented in the schema. The description adds no parameter-level detail beyond that, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and scope: tech stack for a company domain, then enumerates the categories returned (ad pixels, analytics, tag managers, CMS, e-commerce, hosting, payments, plus email provider/SPF/DMARC from DNS). This is specific enough that an agent can tell exactly what comes back and how it differs from profile-oriented siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly gives both the when-to-use and the when-not-to-use with the named alternative: 'Use for technology-only research; use get_company_profile when hiring, ads and contacts are also needed.' The routing rule is stated, not inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Published contacts for a company domain from its home, about, contact, team and careers pages: deduplicated emails and LinkedIn, X and GitHub links, plus MX, SPF and DMARC checks (not mailbox verification). $0.01; nothing found is free.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Bare public company domain whose published contact pages and DNS records should be inspected. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely non-obvious traits: which pages are scraped, that results are deduplicated, and that DNS records are included but mailbox verification is not. The billing model ('$0.01; nothing found is free') is valuable cost context an agent cannot get from structured fields; only rate limits and cross-page dedup rules are left unstated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single dense sentence that front-loads the core purpose, then the output inventory, then the exclusion, then pricing. Every clause carries information; nothing is redundant with the title or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, two-parameter tool with an output schema, the description supplies the remaining decision-relevant facts: source pages, result types, what is deliberately excluded, and the cost/failure pricing. An agent has everything needed to decide to call it and to interpret an empty result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both the required `domain` and optional `context` fully documented in the schema, so the baseline is 3. The description adds only a light gloss on `domain` (public company domain whose contact pages are inspected) and says nothing about `context` beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource (published contacts for a company domain) and enumerates exactly what comes back: deduplicated emails, LinkedIn/X/GitHub links, and MX/SPF/DMARC checks. This clearly separates it from siblings like get_company_profile or private_blind_lookup 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States the intended input context (a public company domain's home/about/contact/team/careers pages) and explicitly excludes a neighbouring use case with 'not mailbox verification', which prevents the agent from expecting deliverability results. It stops short of naming an alternative tool for mailbox verification or for non-public contact discovery, so it is clear context rather than full when/when-not routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Finds which of 2 to 25 company domains are hiring hardest. Step 1 is a free scan that returns each intent_score and a quote_id; step 2 pays $0.25 per hot company (at most 4, $1.00) for a full profile of each. No hot company means no charge. 3 free scans per day.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| domains | No | Public company domains without a URL scheme, path or port. | |
| quote_id | No | quote_id from step 1. Send it alone to pay and receive the results. | |
| min_intent_score | No | Minimum hiring intent score (0–100) for a company to be included in the paid hot-company quote. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well past the annotations by disclosing cost ($0.25 per hot company, capped at $1.00), the no-hot-company no-charge guarantee, and the 3-free-scans-per-day quota — all behavior an agent cannot infer from readOnlyHint/openWorldHint. The only mild tension is that a paid charge is an external side effect even though the tool is flagged read-only for data; that is a scoping convention rather than a direct contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four short sentences, front-loaded with what the tool does, then sequencing, then cost, then quota. Nothing is redundant with the title and every sentence carries operative information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given an output schema, return values need not be explained, and the description still previews intent_score and quote_id. It covers cost, quota, and the step gating completely; only the relationship to neighboring hiring-intent tools is left implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so domains, quote_id, min_intent_score, and context are already documented in the schema. The description reinforces the quote_id handoff role and the 2–25 domain range, but adds no format or threshold detail beyond what the schema states, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource ('Finds which of 2 to 25 company domains are hiring hardest') and immediately frames the two-step scan/quote design. This is distinguishable at a glance from siblings like get_company_hiring_intent, which scores a single company rather than ranking a batch.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The two-step protocol is spelled out concretely: step 1 free scan returns intent_score and quote_id, step 2 redeems the quote_id to pay. It does not, however, tell the agent when to prefer this over get_company_hiring_intent or when a single-company lookup is more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Hiring-based buying-intent score (0-100) for a company domain from its public job board: hiring status, open roles, roles posted in the last 30 days, hiring by function and technologies hired for. $0.01 per result; no board or no open jobs is free. Use to prioritize a known company by hiring signals; use get_company_open_jobs for role listings or get_company_profile for combined research. The score is a heuristic, not confirmed purchase intent.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public company domain without a URL scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only cover readOnly/openWorld; the description adds the non-obvious commercial and epistemic facts: $0.01 per result, free when there is no board or no open jobs, and that the score is a heuristic rather than confirmed purchase intent. Cost and reliability caveats are exactly the context structured fields cannot convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, each load-bearing: what it returns, what it costs, when to use it and what to use instead. The core value proposition is front-loaded in the first clause.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists so return values needn't be explained, yet the description still names the score components, the data source, and the cost model. For a 2-parameter read-only lookup this is everything an agent needs to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the domain parameter is fully documented in the schema (format, maxLength, example); the description adds no further syntax or constraint detail. Baseline 3 applies since the schema carries the parameter burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb-like operation and resource: a hiring-based buying-intent score (0-100) for a company domain sourced from its public job board, with the result's components enumerated. It explicitly distinguishes itself from get_company_open_jobs and get_company_profile, so an agent can pick it without reading sibling schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a positive use case ("prioritize a known company by hiring signals") plus explicit alternatives with the condition that selects each (role listings vs. combined research). Nothing is left to inference about when this tool is the right call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Live open jobs for a company domain from its public Greenhouse, Lever, Ashby, Workable, Recruitee or SmartRecruiters board: titles, departments, locations, remote flag and salary when published. Up to 300 jobs; known_job_ids returns new and closed jobs. $0.01; no board or no open jobs is free. Use for individual role listings; use get_company_hiring_intent for a hiring score or get_company_profile for combined company research.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without a URL scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| diff_only | No | Return only jobs that are not in known_job_ids. Needs known_job_ids. | |
| known_job_ids | No | Job IDs you already have from an earlier call. The answer then lists new and closed job IDs. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint/openWorldHint annotations, the description discloses cost ($0.01, free when no board or no open jobs), the 300-job cap, and the diff semantics of known_job_ids returning new and closed jobs. Cost and truncation limits are behavioral traits the annotations do not carry, and there is no contradiction with readOnlyHint=true.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each carrying load: capability+providers+fields, then limits and pricing, then routing to siblings. Slightly dense in the first sentence but front-loaded with the core verb and resource, with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 needn't be explained, and the description covers everything else an agent needs: data sources, field set, result cap, diff workflow, cost, failure/free case, and sibling alternatives. Nothing material is missing for a read-only lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all four parameters are already documented, and the description mostly restates what the schema says about known_job_ids ("returns new and closed jobs") and diff_only. It adds no syntax, ID format, or example detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ("Live open jobs for a company domain") and names the six source providers (Greenhouse, Lever, Ashby, Workable, Recruitee, SmartRecruiters) plus the fields returned. It is clearly distinguishable from get_company_hiring_intent and get_company_profile, which are named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The final sentence gives an explicit routing rule: "Use for individual role listings; use get_company_hiring_intent for a hiring score or get_company_profile for combined company research." Both alternatives and the condition that selects them are stated, leaving nothing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
One-call company profile for a domain: tech stack, hiring intent, Google Ads and published contacts (emails, social links, MX), run in parallel, with plain-language signals and a breakout_summary growth estimate. $0.03, charged only when at least two of the four sections have data. Counts as one of the 5 free daily calls. Start here for one company across all four signals; use a single-signal tool for narrower research, batch_lookup for several known domains, or company_footprint_check for found/not_found evidence only. Growth signals are estimates, not financial forecasts.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public company domain without a URL scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnly/openWorld annotations, it discloses price ($0.03), the conditional billing rule (charged only when at least two of four sections have data), the free-tier consumption (one of 5 daily calls), parallel execution, and the estimation caveat on growth signals. That's exactly the kind of cost and output-reliability context an agent can't infer from annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose and output list, and every sentence adds routing, pricing, or caveat value. It is dense — pricing, quota, and caveat details are packed into a single long span — but little could be cut without losing decision-relevant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given an output schema exists, the description doesn't need to explain return shapes; instead it covers cost model, quota impact, estimation disclaimers, and sibling routing. Nothing an agent needs before calling is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents the domain format and the optional context field; the description only implies the domain input without adding format or validation detail. Baseline 3 is appropriate since the schema carries the parameter burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('One-call company profile for a domain') and enumerates exactly what it returns (tech stack, hiring intent, Google Ads, published contacts). It also names the narrower siblings it supersedes, so it's unmistakable in the toolset.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to start here for a single company across all four signals, then routes to single-signal tools for narrower research, batch_lookup for several known domains, and company_footprint_check for found/not_found only. Both when-to-use and when-not-to-use are covered with named alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Extract an OTP candidate from a received message in your existing inbox. Optionally pass message_id to select a message; use list_email_messages to inspect messages first. Pass inbox_id, capability and access_token from create_email_inbox. No additional charge. Poll at least 2 seconds apart; back off on 429/503. Pending, no_code or ambiguous does not confirm a usable OTP; external code acceptance is not guaranteed.
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | inbox_id parameter for get_email_code | |
| capability | Yes | capability parameter for get_email_code | |
| message_id | No | message_id parameter for get_email_code | |
| access_token | No | Use the scoped access_token returned by create_email_inbox. Optional only for an existing provisioned private pilot connection. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=true, destructiveHint=false and openWorldHint=false already established by annotations, the description adds important behavioral context: no additional charge, polling cadence, backoff behavior, and the caveat that pending, no_code or ambiguous does not confirm a usable OTP. It also warns that external code acceptance is not guaranteed, which is valuable for an extraction tool whose result may be unusable even after a successful call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but front-loaded and every sentence carries operational value: message selection, credential source, rate-limit behavior, and OTP-status caveats. There is no filler or repetition of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The annotations cover the safety profile and an output schema exists, so the description does not need to explain return values. It still provides the missing operational context an agent needs: where credentials come from, how to choose a message, polling behavior, and what ambiguous extraction states mean.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameter names and types are already well documented, establishing a baseline of 3. The description adds meaningful provenance by saying inbox_id, capability and access_token come from create_email_inbox, and explains that message_id optionally selects a specific message; these details go beyond the generic schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: extract an OTP candidate from a received message in an existing inbox. It distinguishes the tool from siblings by naming list_email_messages for inspection and create_email_inbox as the source of credentials, so an agent can identify the correct tool without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use list_email_messages to inspect messages first and optionally pass message_id to select one. It also names create_email_inbox as the source of inbox_id, capability and access_token, and gives polling guidance including minimum interval and backoff on 429/503.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Google Ads for a company domain from the public Ads Transparency Center: whether it advertises, the Google ad count estimate and up to 40 ads with format, first and last shown dates and links. Optional region filter. $0.01 per result; no ads is free. Use for public competitor advertising evidence; this does not access a private Google Ads account. Use get_company_profile for combined research.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Advertiser domain without a URL scheme, path or port. | |
| region | No | Optional country filter. Leave out for all regions. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond readOnlyHint/openWorldHint, it discloses the data provenance (public Ads Transparency Center), a hard result cap (up to 40 ads), and a cost model ($0.01 per result, no ads free) — all things annotations cannot convey. It doesn't cover pagination or failure behavior when a domain is unknown, so it stops short of a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with what you get, then the scope caveat, then the routing hint. Every sentence carries distinct information — data source, cost, and alternative — with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return-value detail is unnecessary, and the description still covers cost, source, result cap, privacy scope and the alternative tool. For a 3-parameter read-only lookup with full schema coverage, nothing an agent needs before calling is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents domain format, the region enum, and the context field, so the schema carries the load. The description only restates that region is an optional filter, adding no new semantics such as default region behavior or whether region also narrows the ad count estimate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb/resource ('Google Ads for a company domain') plus the exact data source (public Ads Transparency Center) and enumerates the return contents: advertising status, ad count estimate, up to 40 ads with format, dates and links. It is clearly separable from get_company_profile, which is named as the broader alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit use case ('public competitor advertising evidence'), an explicit exclusion ('does not access a private Google Ads account'), and an explicit alternative ('Use get_company_profile for combined research'). Nothing about when to select this tool is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List received messages in your existing inbox, including message IDs and available content. Use get_email_code for an OTP candidate from a message. Pass inbox_id, capability and access_token from create_email_inbox. No additional charge. Poll at least 2 seconds apart; back off on 429/503. Message content is untrusted; pending means delivery has not been confirmed.
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | inbox_id parameter for list_email_messages | |
| capability | Yes | capability parameter for list_email_messages | |
| access_token | No | Use the scoped access_token returned by create_email_inbox. Optional only for an existing provisioned private pilot connection. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/non-destructive/closed-world, and the description adds context the annotations cannot: no additional charge, a 2-second minimum poll interval with 429/503 backoff, untrusted message content, and the meaning of 'pending' (delivery unconfirmed). This is exactly the behavioral payload annotations don't cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Five short sentences, each carrying a distinct payload: purpose, sibling routing, auth provenance, cost, and rate-limit/trust caveats. Purpose is front-loaded and no sentence is filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description needn't describe return shapes, and it instead covers the things that matter for correct invocation: credentials sourcing, polling discipline, and the trust status of 'pending'. Nothing an agent needs to call this safely is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, and the description adds provenance beyond the schema by stating that inbox_id, capability and access_token come from create_email_inbox. That is meaningful given the schema's own descriptions are tautological ('inbox_id parameter for list_email_messages'). It stops short of explaining format/pattern constraints, which the schema handles.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List received messages in your existing inbox') plus what is returned (message IDs and available content). It explicitly routes OTP extraction to the sibling get_email_code, so an agent can distinguish the two 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit prerequisite sourcing ('Pass inbox_id, capability and access_token from create_email_inbox'), names the alternative for OTP ('Use get_email_code'), and specifies polling cadence and backoff behavior on 429/503. No usage decision is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Store audit for shopping agents: machine-readable product data, UCP/ACP discovery, payment hints and robots.txt access, with a heuristic score and prioritized fixes. Not a certification or checkout test. $0.01 per result. Use to diagnose agent-readable store discovery and prioritize fixes; use universal_product_url_to_json for one product or pre_purchase_merchant_trust_check for purchase-risk evidence. Does not modify the store.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description adds material context beyond them: cost ('$0.01 per result'), the non-mutating guarantee ('Does not modify the store'), the heuristic (not authoritative) nature of the score, and that unknowns are surfaced explicitly. That is exactly the kind of pricing and confidence disclosure annotations cannot carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with scope and outputs, then alternatives, then exclusions, with no filler. Dense but every clause carries information; the opening 'Returns structured public evidence and explicit unknowns' is the only mildly abstract sentence before the concrete list arrives.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shape needn't be described, and annotations cover safety. With both parameters documented at 100% coverage and the description adding cost, scope, and sibling routing, an agent has everything needed to call this correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the domain parameter is fully documented ('Public domain without scheme, path or port'), so the schema does the heavy lifting. The description adds no format or constraint detail beyond what the schema already states, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Store audit for shopping agents') and enumerates the concrete signals checked: machine-readable product data, UCP/ACP discovery, payment hints, robots.txt, plus a heuristic score and prioritized fixes. An agent can separate this from siblings like agentic_shelf_schema_comparator without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'Use to diagnose agent-readable store discovery and prioritize fixes; use universal_product_url_to_json for one product or pre_purchase_merchant_trust_check for purchase-risk evidence.' It also carves out what it is not ('Not a certification or checkout test'), covering both when-to-use and when-not.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Store check for schema gaps, Google ad activity and public business contacts; a lead qualifies only with ad and SEO evidence. Public emails are not verified decision makers. $0.05 per qualified result. Use to qualify a known store for outreach about schema gaps; use muse_agentic_store_readiness_auditor for an audit without lead qualification or extract_company_contacts for contacts only. Does not send outreach or measure conversion loss.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only cover readOnly and openWorld, but the description adds substantive behavior: pricing at $0.05 per qualified result, the qualification gate, the evidence-vs-unknowns output posture, and the caveat that public emails are not verified decision makers. That caveat is exactly the kind of risk context annotations cannot carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Dense and largely front-loaded, with qualification criteria and pricing stated early. The opener 'Returns structured public evidence and explicit unknowns' is abstract and slightly awkward, but every remaining sentence carries real information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shape need not be explained; the description supplies what the schema cannot – qualification criteria, cost, evidence caveats, and exclusions. An agent has everything needed to decide and call correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both the domain format and the optional context field are already documented. The description implies the input is a known store domain but adds no syntax or format detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (a known store) and a specific output (public evidence of schema gaps, Google ad activity, contacts) with an explicit qualification rule: a lead qualifies only with ad and SEO evidence. It is easily distinguished from siblings like muse_agentic_store_readiness_auditor and extract_company_contacts, which are named directly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit 'use to qualify a known store for outreach about schema gaps' plus two named alternatives with the conditions that select them (audit without lead qualification; contacts only). It also states a negative scope – does not send outreach or measure conversion loss – closing the obvious misuse paths.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Public trust evidence for an unfamiliar online shop before buying: a cautious evidence score, risk flags, missing signals and limits. Cannot certify safety. $0.005 after the shared free calls. x402 API endpoints: x402_merchant_trust_check. Use for a consumer purchase from an unfamiliar shop; use b2b_vendor_stability_evaluator for B2B supplier procurement. This does not buy goods or authorize payment.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| merchant_wallet_or_id | No | Optional merchant identifier as context; supplying a wallet does not establish ownership or on-chain reputation. | |
| transaction_amount_usd | No | Optional intended purchase value in USD as context; it does not authorize a purchase or change the scan price. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=true and openWorldHint=true already declared, the description adds important behavioral context: it returns explicit unknowns, cannot certify safety, costs $0.005 after shared free calls, and does not buy goods or authorize payment. These details clarify the tool's limits and cost without contradicting the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description front-loads the core return value and then covers limits, pricing, endpoint alias, and usage guidance. It is mostly efficient, though there is some redundancy between 'structured public evidence' and 'Public trust evidence' and the endpoint mention could be clearer.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the existing output schema, read-only annotations, and fully documented parameters, the description supplies the remaining decision-critical context: purpose, scope, cost, safety limits, and B2B alternative. An agent has enough information to decide when and how to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 the domain, context, merchant identifier, and transaction amount parameters in detail. The description provides only general framing around public trust evidence for an online shop and does not add parameter-specific semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific resource and outcome: public trust evidence, a cautious evidence score, risk flags, missing signals and limits for an unfamiliar online shop before buying. It distinguishes the consumer-purchase use case from B2B supplier procurement by naming the b2b_vendor_stability_evaluator sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use this tool for a consumer purchase from an unfamiliar shop and names b2b_vendor_stability_evaluator for B2B supplier procurement. It also clarifies that the tool does not buy goods or authorize payment, though it does not explain when to choose this over the x402_merchant_trust_check sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Blind lookup proxy: the target is removed from x402 facilitator metadata (HirePulse and the destination still see it). Arguments are tool and target only. $0.02 single check; company_profile and due_diligence use the $0.04 bundle tier, set by the X-Private-Query-Tier header or MCP metadata hirepulse/private-tier. Use only when hiding the target from facilitator metadata is required; use the direct single-signal tools or get_company_profile otherwise. It does not hide the target from HirePulse or the destination.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | Lookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata. | |
| target | Yes | Bare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond readOnlyHint and openWorldHint, the description discloses the privacy boundary, pricing tiers, the header/metadata mechanism for bundle pricing, and the limited argument shape. It does not contradict the annotations; it substantially enriches the behavioral context an agent needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The purpose and privacy effect are front-loaded, followed by argument shape, pricing, usage guidance, and limitation. The paragraph is dense but has no redundant sentences; each clause contributes operational or routing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given annotations, full schema coverage, and an output schema, the description covers what an agent must know: what is hidden, what is not hidden, when to use it, what alternatives exist, and how tier pricing is selected. No material gap remains for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already explains both tool and target, including the enum and target format. The description adds only the high-level constraint that arguments are tool and target only, plus privacy context, so it does not need to compensate for missing parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific proxy operation and names the exact privacy effect: removing the target from x402 facilitator metadata. It also distinguishes this tool from direct single-signal tools and get_company_profile, so an agent can identify its role without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit condition for use ('only when hiding the target from facilitator metadata is required') and names the alternatives for the default case. It also clarifies the important boundary that HirePulse and the destination still see the target, preventing misuse based on a false privacy assumption.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Product page to JSON: price, stock, variants, ratings and shipping evidence from JSON-LD, Microdata and OpenGraph, without a browser. Missing facts are null. $0.002 per result. Use for one product detail URL; use agentic_shelf_schema_comparator for a cross-store comparison or muse_agentic_store_readiness_auditor for a store-wide discovery audit.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| product_url | Yes | Public HTTP(S) product detail URL to extract structured product evidence from; use a product page rather than a store homepage. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint/openWorldHint annotations, it discloses behavior that matters for planning: no browser is used, missing facts are returned as null, and each result costs $0.002. The null-vs-omitted contract and per-call price are exactly the kind of operational context annotations cannot express.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Information is front-loaded and every clause carries substance (fields, sources, null contract, price, alternatives). The opening 'Returns structured public evidence and explicit unknowns' is somewhat abstract preamble before the concrete restatement, a minor redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-URL extraction tool with full schema coverage, annotations, and an output schema, the description supplies everything else an agent needs: data sources, null semantics, cost, no-browser constraint, and routing to alternatives.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both parameters are already fully documented in the input schema, including the product-page-vs-homepage hint. The description reinforces 'one product detail URL' but adds no format or syntax detail beyond the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (product page URL -> structured JSON) and enumerates the extracted fields (price, stock, variants, ratings, shipping) plus the source formats (JSON-LD, Microdata, OpenGraph). It explicitly names the two sibling tools it is not, so an agent can disambiguate without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear positive condition ('one product detail URL') and two explicit alternatives with their selecting conditions (cross-store comparison -> agentic_shelf_schema_comparator; store-wide audit -> muse_agentic_store_readiness_auditor). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Public web page to clean Markdown with title, meta description and a token estimate; scripts, navigation and ads removed. max_chars 1 to 100000 (default 15000). $0.002; empty results are free.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP(S) page URL to convert to Markdown; private addresses, unsafe redirects and credential-bearing URLs are rejected. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| max_chars | No | Maximum characters of Markdown to return; longer pages are truncated and marked as such. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds substantial behavior beyond the annotations: it says scripts, navigation, and ads are removed; title, meta description, and token estimate are included; truncation is marked; and pricing is $0.002 with empty results free. These details are highly useful for an agent deciding whether and how to call the tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single dense sentence that front-loads the core operation and then adds the most decision-relevant constraints: output cleanliness, max_chars range, and cost. Every clause carries useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 100% schema coverage, an output schema, and annotations covering read-only/open-world behavior, the description supplies the remaining decision-critical context: public-page scope, cleaning behavior, truncation, token estimate, and pricing. An agent has enough information to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 url, context, and max_chars thoroughly. The description restates max_chars bounds and default and adds the pricing note, but it does not add parameter meaning beyond what the schema provides; baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that it converts a public web page into clean Markdown, including title, meta description, and token estimate, while removing scripts, navigation, and ads. It is specific about the operation and output traits, but it does not distinguish itself from possible sibling URL-conversion tools such as universal_product_url_to_json.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word 'Public' implies that private pages are out of scope, and the pricing note helps frame usage economics. However, there is no explicit when-to-use guidance, no stated alternatives, and no when-not-to-use conditions beyond the public-page constraint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns structured public evidence and explicit unknowns. Signed public-evidence statement for a merchant domain, with expiry and a public verification key. It proves HirePulse issued the assessment, not ownership or purchase safety. $0.005 per result. Use when you need a portable signed assessment; use pre_purchase_merchant_trust_check for risk evidence without a badge or x402_merchant_trust_check for an API endpoint. It does not issue a third-party certification.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Public domain without scheme, path or port. | |
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnly and openWorld; the description adds cost ($0.005 per result), the nature of the output artifact (signed, with expiry and public verification key), and an explicit disclaimer of what the signature implies. That disclaimer is materially useful because an agent could otherwise over-interpret 'verified' as a purchase-safety certification.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the artifact definition, then pricing, then routing to alternatives. The opening sentence ("Returns structured public evidence and explicit unknowns") is somewhat redundant with the sentence that follows and with the output schema, but the remaining prose is dense and purposeful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, so return values needn't be explained, and the description still covers cost, safety profile, artifact scope, and alternatives. The only minor gap is the concrete format of the badge (signed payload vs. URL), though 'signed public-evidence statement with expiry and public verification key' is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both parameters are documented there (domain format, optional context). The description adds no additional parameter guidance, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: a signed public-evidence statement for a merchant domain, with expiry and a verification key. It immediately scopes what the artifact proves (HirePulse issued the assessment) versus what it does not (ownership or purchase safety), which distinguishes it from generic merchant-trust siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly names the selection condition ("Use when you need a portable signed assessment") and names two alternatives with their respective conditions: pre_purchase_merchant_trust_check for risk evidence without a badge, and x402_merchant_trust_check for an API endpoint. Negative scoping is also stated ("does not issue a third-party certification").
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Pre-payment check of an x402 API endpoint: discovery files, live 402 terms, comparable USDC prices, latency, prompt-injection flags and public Coinbase CDP Bazaar payment statistics for the host. Heuristic, not a guarantee. $0.002; unreachable targets are free. Online shops: pre_purchase_merchant_trust_check.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data. | |
| target_url | Yes | Public HTTPS x402 API endpoint to inspect before signing a payment authorization; this scan does not authorize payment. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only give readOnlyHint and openWorldHint; the description adds material context beyond them: a per-call price, a free-on-unreachable pricing exception, an explicit epistemic caveat ('Heuristic, not a guarantee'), and the assurance that the scan does not itself authorize payment. These are exactly the traits an agent needs before spending money on a scan.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, all load-bearing, with the scope constraint and price front-loaded before the sibling routing. The first sentence is a heavy enumeration, but each listed check maps to a real capability rather than padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output shape is covered by the output schema, so the description only needs to convey purpose, cost, limits, and alternatives — all present. An agent can decide, pay for, and interpret this call without opening anything else.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so target_url and context are already documented in the schema, and the description adds no syntax, format, or constraint detail beyond them. Baseline 3 applies because the schema carries the parameter burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Pre-payment check of an x402 API endpoint') and enumerates exactly what is inspected: discovery files, live 402 terms, USDC prices, latency, prompt-injection flags, and CDP Bazaar statistics. It explicitly distinguishes itself from the closest sibling by routing online shops to pre_purchase_merchant_trust_check.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is anchored to a concrete decision point ('before signing a payment authorization'), with an explicit alternative named for the adjacent use case ('Online shops: pre_purchase_merchant_trust_check'). The cost/refund rule ('$0.002; unreachable targets are free') further informs the call decision.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.000_ask_hirepulse_advisoragentic_shelf_schema_comparator8 fields changedInput schema / properties / competitor_domains / descriptionAdded value: +"One to three distinct bare public competitor store domains to compare against domain; one product is sampled per store."Input schema / properties / competitor_domains / items / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Input schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "comparison": {
+ "items": {
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "readiness_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "structured_fields": {
+ "type": "object"
+ }
+ },
+ "required": [
+ "domain",
+ "readiness_score",
+ "structured_fields"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ },
+ "stores": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "comparison": {
- "items": {
- "properties": {
- "domain": {
- "type": "string"
- },
- "readiness_score": {
- "type": [
- "number",
- "null"
- ]
- },
- "structured_fields": {
- "type": "object"
- }
- },
- "required": [
- "domain",
- "readiness_score",
- "structured_fields"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- },
- "stores": {
- "items": {
- "type": "object"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]ask_hirepulse_advisor7 fields changedInput schema / properties / agent_goal / descriptionAdded value: +"Describe the research goal so the advisor can recommend a tool and estimate its list price."Input schema / properties / budget_usd / descriptionAdded value: +"Optional USD budget used for recommendations only; this does not authorize spending or payment."Input schema / properties / domain_count / descriptionAdded value: +"Number of companies you plan to research, used for batch sizing and cost estimates."Input schema / properties / sample_domain / descriptionAdded value: +"Optional bare public company domain for a concrete request example and existing cached hints; no new lookup is run."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "alternatives": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "cached_hint": {
+ "description": "Today only, status metadata; no result data or new engine calls.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "cost_estimate_usd": {
+ "description": "List-price range before free quota, actual data availability and optional follow-up calls; includes request splitting and scan limits.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "efficiency_analysis": {
+ "properties": {
+ "company_profile": {
+ "type": "object"
+ },
+ "comparison": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "note": {
+ "type": "string"
+ },
+ "separately": {
+ "type": "object"
+ }
+ },
+ "required": [
+ "company_profile",
+ "separately",
+ "comparison",
+ "note"
+ ],
+ "type": "object"
+ },
+ "free_quota": {
+ "properties": {
+ "limit": {
+ "type": "integer"
+ },
+ "message": {
+ "type": "string"
+ },
+ "note": {
+ "type": "string"
+ },
+ "remaining": {
+ "description": "Successful free calls remaining, or null when quota storage is unavailable.",
+ "minimum": 0,
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "resets_at": {
+ "format": "date-time",
+ "type": "string"
+ }
+ },
+ "required": [
+ "remaining",
+ "limit",
+ "resets_at",
+ "message",
+ "note"
+ ],
+ "type": "object"
+ },
+ "guarantees": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "recommended_execution_sequence": {
+ "items": {
+ "properties": {
+ "body": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "mcp_tool": {
+ "type": "string"
+ },
+ "next_tool_call_payload": {
+ "description": "Exact executable request body when inputs are available; null until required_input is provided. Never contains invented domains or quote IDs.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "note": {
+ "type": "string"
+ },
+ "phase": {
+ "type": "string"
+ },
+ "required_input": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "tool",
+ "mcp_tool",
+ "url",
+ "body",
+ "next_tool_call_payload",
+ "required_input"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "recommended_tool": {
+ "description": "Recommended data tool, or null when the goal is unclear.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tools": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "why": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "recommended_tool",
+ "why",
+ "alternatives",
+ "efficiency_analysis",
+ "cost_estimate_usd",
+ "free_quota",
+ "recommended_execution_sequence",
+ "cached_hint",
+ "guarantees"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "alternatives": {
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "cached_hint": {
- "description": "Today only, status metadata; no result data or new engine calls.",
- "type": [
- "object",
- "null"
- ]
- },
- "cost_estimate_usd": {
- "description": "List-price range before free quota, actual data availability and optional follow-up calls; includes request splitting and scan limits.",
- "type": [
- "object",
- "null"
- ]
- },
- "efficiency_analysis": {
- "properties": {
- "company_profile": {
- "type": "object"
- },
- "comparison": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "note": {
- "type": "string"
- },
- "separately": {
- "type": "object"
- }
- },
- "required": [
- "company_profile",
- "separately",
- "comparison",
- "note"
- ],
- "type": "object"
- },
- "free_quota": {
- "properties": {
- "limit": {
- "type": "integer"
- },
- "message": {
- "type": "string"
- },
- "note": {
- "type": "string"
- },
- "remaining": {
- "minimum": 0,
- "type": "integer"
- },
- "resets_at": {
- "format": "date-time",
- "type": "string"
- }
- },
- "required": [
- "remaining",
- "limit",
- "resets_at",
- "message",
- "note"
- ],
- "type": "object"
- },
- "guarantees": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "recommended_execution_sequence": {
- "items": {
- "properties": {
- "body": {
- "type": [
- "object",
- "null"
- ]
- },
- "mcp_tool": {
- "type": "string"
- },
- "next_tool_call_payload": {
- "description": "Exact executable request body when inputs are available; null until required_input is provided. Never contains invented domains or quote IDs.",
- "type": [
- "object",
- "null"
- ]
- },
- "note": {
- "type": "string"
- },
- "phase": {
- "type": "string"
- },
- "required_input": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "tool": {
- "type": "string"
- },
- "url": {
- "format": "uri",
- "type": "string"
- }
- },
- "required": [
- "tool",
- "mcp_tool",
- "url",
- "body",
- "next_tool_call_payload",
- "required_input"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "recommended_tool": {
- "description": "Recommended data tool, or null when the goal is unclear.",
- "type": [
- "string",
- "null"
- ]
- },
- "tools": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "why": {
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "recommended_tool",
- "why",
- "alternatives",
- "efficiency_analysis",
- "cost_estimate_usd",
- "free_quota",
- "recommended_execution_sequence",
- "cached_hint",
- "guarantees"
-]b2b_vendor_stability_evaluator6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / vendor_domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "engineering_and_support_headcount_trend": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "hiring_velocity": {
+ "type": "object"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "seo_visibility_trend": {
+ "type": "string"
+ },
+ "stability_status": {
+ "enum": [
+ "GROWING",
+ "STABLE",
+ "CONTRACTING",
+ "HIGH_RISK",
+ "UNKNOWN"
+ ],
+ "type": "string"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ },
+ "tech_stack_summary": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "vendor_domain": {
+ "type": "string"
+ },
+ "vendor_health_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "verified_contacts_available": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "engineering_and_support_headcount_trend": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "hiring_velocity": {
- "type": "object"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "seo_visibility_trend": {
- "type": "string"
- },
- "stability_status": {
- "enum": [
- "GROWING",
- "STABLE",
- "CONTRACTING",
- "HIGH_RISK",
- "UNKNOWN"
- ],
- "type": "string"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- },
- "tech_stack_summary": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "vendor_domain": {
- "type": "string"
- },
- "vendor_health_score": {
- "type": [
- "number",
- "null"
- ]
- },
- "verified_contacts_available": {
- "type": [
- "boolean",
- "null"
- ]
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]batch_lookup5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / tool / descriptionAdded value: +"Data tool to run for each domain during quote creation; omit when redeeming a quote_id."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "billable_count": {
+ "type": "integer"
+ },
+ "cold": {
+ "description": "hot-buyers: domains below the threshold, free.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "expires_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "next": {
+ "type": "string"
+ },
+ "price_micro_usd": {
+ "type": "integer"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "quote_id": {
+ "type": "string"
+ },
+ "results": {
+ "description": "Paid rows, after step 2.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
+ "enum": [
+ "quote",
+ "nothing_billable",
+ "ok"
+ ],
+ "type": "string"
+ },
+ "statuses": {
+ "description": "Status of every domain, free.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "billable_count": {
- "type": "integer"
- },
- "cold": {
- "description": "hot-buyers: domains below the threshold, free.",
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "expires_at": {
- "format": "date-time",
- "type": "string"
- },
- "next": {
- "type": "string"
- },
- "price_micro_usd": {
- "type": "integer"
- },
- "price_usd": {
- "type": "number"
- },
- "quote_id": {
- "type": "string"
- },
- "results": {
- "description": "Paid rows, after step 2.",
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "status": {
- "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
- "enum": [
- "quote",
- "nothing_billable",
- "ok"
- ],
- "type": "string"
- },
- "statuses": {
- "description": "Status of every domain, free.",
- "items": {
- "type": "object"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "status"
-]checkout_active_promo_code_finder7 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Input schema / properties / product_category / descriptionAdded value: +"Optional category context for the supplied store; does not guarantee category-specific or checkout-verified coupons."Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "active_codes": {
+ "items": {
+ "properties": {
+ "checkout_verified": {
+ "type": "boolean"
+ },
+ "code": {
+ "type": "string"
+ },
+ "confidence": {
+ "maximum": 1,
+ "minimum": 0,
+ "type": "number"
+ },
+ "discount_description": {
+ "type": "string"
+ },
+ "promo_landing_url": {
+ "type": "string"
+ },
+ "source": {
+ "enum": [
+ "seo_meta"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "discount_description",
+ "source",
+ "promo_landing_url",
+ "confidence",
+ "checkout_verified"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "best_offer_summary": {
+ "type": "string"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "promos_found": {
+ "type": "boolean"
+ },
+ "sources_checked": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "active_codes": {
- "items": {
- "properties": {
- "checkout_verified": {
- "type": "boolean"
- },
- "code": {
- "type": "string"
- },
- "confidence": {
- "maximum": 1,
- "minimum": 0,
- "type": "number"
- },
- "discount_description": {
- "type": "string"
- },
- "promo_landing_url": {
- "type": "string"
- },
- "source": {
- "enum": [
- "seo_meta"
- ],
- "type": "string"
- }
- },
- "required": [
- "code",
- "discount_description",
- "source",
- "promo_landing_url",
- "confidence",
- "checkout_verified"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "best_offer_summary": {
- "type": "string"
- },
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "promos_found": {
- "type": "boolean"
- },
- "sources_checked": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]claim_free_trialcompany_footprint_check4 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "breakout_summary": {
+ "description": "get_company_profile only. Growth estimate from public signals (hiring, Google Ads, site maturity); not investment advice.",
+ "properties": {
+ "method": {
+ "type": "string"
+ },
+ "reasons": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "signal": {
+ "enum": [
+ "strong",
+ "moderate",
+ "weak",
+ "none",
+ "insufficient_data"
+ ],
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "contacts": {
+ "description": "get_company_profile only. Same fields as extract_company_contacts.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "domain": {
+ "type": "string"
+ },
+ "footprint": {
+ "description": "found, not_found or unknown for each public signal.",
+ "properties": {
+ "google_ads": {
+ "type": "string"
+ },
+ "job_board_with_open_roles": {
+ "type": "string"
+ },
+ "website_ad_or_analytics_tags": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "google_ads": {
+ "description": "Same fields as get_google_ads_by_domain.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "hiring_intent": {
+ "description": "Same fields as get_company_hiring_intent.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sections_status": {
+ "additionalProperties": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "sections_with_data": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "signals": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Only ok is charged: at least two sections have data (of four for get_company_profile, three for company_footprint_check).",
+ "enum": [
+ "ok",
+ "insufficient_data"
+ ],
+ "type": "string"
+ },
+ "tech_stack": {
+ "description": "Same fields as detect_website_tech_stack.",
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "sections_status",
+ "checked_at"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "domain": {
- "type": "string"
- },
- "footprint": {
- "description": "found, not_found or unknown for each public signal.",
- "properties": {
- "google_ads": {
- "type": "string"
- },
- "job_board_with_open_roles": {
- "type": "string"
- },
- "website_ad_or_analytics_tags": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "google_ads": {
- "description": "Same fields as get_google_ads_by_domain.",
- "type": [
- "object",
- "null"
- ]
- },
- "hiring_intent": {
- "description": "Same fields as get_company_hiring_intent.",
- "type": [
- "object",
- "null"
- ]
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "sections_status": {
- "additionalProperties": {
- "type": "string"
- },
- "type": "object"
- },
- "sections_with_data": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "signals": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "description": "Only ok is charged: at least two of the three sections have data.",
- "enum": [
- "ok",
- "insufficient_data"
- ],
- "type": "string"
- },
- "tech_stack": {
- "description": "Same fields as detect_website_tech_stack.",
- "type": [
- "object",
- "null"
- ]
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "sections_status",
- "checked_at"
-]create_email_inboxdelete_email_inboxdetect_website_tech_stack6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "notion.so"
+]Output schema / additionalPropertiesRemoved value: -falseOutput schema / anyOfAdded value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "ad_pixels": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "added": {
+ "items": {
+ "type": "string"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "analytics": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "apify_alternative": {
+ "properties": {
+ "url": {
+ "type": "string"
+ },
+ "when": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "url",
+ "when"
+ ],
+ "type": "object"
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "cms": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dmarc_policy": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "domain": {
+ "type": "string"
+ },
+ "ecommerce": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "email_provider": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "final_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "frameworks": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "has_ga4": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "has_google_ads_tag": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "has_gtm": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "has_linkedin_insight": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "has_meta_pixel": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "has_tiktok_pixel": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "hosting_cdn": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "is_first_run": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "marketing_tools": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "next_steps": {
+ "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
+ "items": {
+ "properties": {
+ "body": {
+ "type": "object"
+ },
+ "mcp_tool": {
+ "type": "string"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "why": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payments": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "recommended_next_step": {
+ "properties": {
+ "body": {
+ "type": "object"
+ },
+ "price_usd": {
+ "minimum": 0,
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "zero_result_zero_charge": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "tool",
+ "url",
+ "body",
+ "price_usd",
+ "zero_result_zero_charge"
+ ],
+ "type": "object"
+ },
+ "removed": {
+ "items": {
+ "type": "string"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ },
+ "spf_senders": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Only ok is charged. no_signals: the page loaded but no technology was detected.",
+ "enum": [
+ "ok",
+ "no_signals",
+ "blocked",
+ "unreachable",
+ "not_found"
+ ],
+ "type": "string"
+ },
+ "technology_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "verified_services": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "final_url",
+ "title",
+ "cms",
+ "ecommerce",
+ "email_provider",
+ "dmarc_policy",
+ "note",
+ "technology_count",
+ "checked_at",
+ "added",
+ "removed",
+ "is_first_run",
+ "has_meta_pixel",
+ "has_google_ads_tag",
+ "has_ga4",
+ "has_gtm",
+ "has_linkedin_insight",
+ "has_tiktok_pixel",
+ "ad_pixels",
+ "analytics",
+ "marketing_tools",
+ "hosting_cdn",
+ "frameworks",
+ "payments",
+ "spf_senders",
+ "verified_services"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "ad_pixels": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "added": {
- "items": {
- "type": "string"
- },
- "type": [
- "array",
- "null"
- ]
- },
- "analytics": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "cms": {
- "type": [
- "string",
- "null"
- ]
- },
- "dmarc_policy": {
- "type": [
- "string",
- "null"
- ]
- },
- "domain": {
- "type": "string"
- },
- "ecommerce": {
- "type": [
- "string",
- "null"
- ]
- },
- "email_provider": {
- "type": [
- "string",
- "null"
- ]
- },
- "final_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "frameworks": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "has_ga4": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "has_google_ads_tag": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "has_gtm": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "has_linkedin_insight": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "has_meta_pixel": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "has_tiktok_pixel": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "hosting_cdn": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "is_first_run": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "marketing_tools": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "next_steps": {
- "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
- "items": {
- "properties": {
- "body": {
- "type": "object"
- },
- "mcp_tool": {
- "type": "string"
- },
- "price_usd": {
- "type": "number"
- },
- "tool": {
- "type": "string"
- },
- "url": {
- "type": "string"
- },
- "why": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "payments": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "removed": {
- "items": {
- "type": "string"
- },
- "type": [
- "array",
- "null"
- ]
- },
- "spf_senders": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "description": "Only ok is charged. no_signals: the page loaded but no technology was detected.",
- "enum": [
- "ok",
- "no_signals",
- "blocked",
- "unreachable",
- "not_found"
- ],
- "type": "string"
- },
- "technology_count": {
- "minimum": 0,
- "type": "integer"
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "verified_services": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "final_url",
- "title",
- "cms",
- "ecommerce",
- "email_provider",
- "dmarc_policy",
- "note",
- "technology_count",
- "checked_at",
- "added",
- "removed",
- "is_first_run",
- "has_meta_pixel",
- "has_google_ads_tag",
- "has_ga4",
- "has_gtm",
- "has_linkedin_insight",
- "has_tiktok_pixel",
- "ad_pixels",
- "analytics",
- "marketing_tools",
- "hosting_cdn",
- "frameworks",
- "payments",
- "spf_senders",
- "verified_services"
-]extract_company_contacts5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / descriptionAdded value: +"Bare public company domain whose published contact pages and DNS records should be inspected."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "dmarc": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "email_deliverable": {
+ "type": "boolean"
+ },
+ "emails": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "inferred_email_pattern": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "mx": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "social_links": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "spf": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "dmarc": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "domain": {
- "type": "string"
- },
- "email_deliverable": {
- "type": "boolean"
- },
- "emails": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "inferred_email_pattern": {
- "type": [
- "string",
- "null"
- ]
- },
- "mx": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "social_links": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "spf": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]find_hot_buyers5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / min_intent_score / descriptionAdded value: +"Minimum hiring intent score (0–100) for a company to be included in the paid hot-company quote."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "billable_count": {
+ "type": "integer"
+ },
+ "cold": {
+ "description": "hot-buyers: domains below the threshold, free.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "expires_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "next": {
+ "type": "string"
+ },
+ "price_micro_usd": {
+ "type": "integer"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "quote_id": {
+ "type": "string"
+ },
+ "results": {
+ "description": "Paid rows, after step 2.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
+ "enum": [
+ "quote",
+ "nothing_billable",
+ "ok"
+ ],
+ "type": "string"
+ },
+ "statuses": {
+ "description": "Status of every domain, free.",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "billable_count": {
- "type": "integer"
- },
- "cold": {
- "description": "hot-buyers: domains below the threshold, free.",
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "expires_at": {
- "format": "date-time",
- "type": "string"
- },
- "next": {
- "type": "string"
- },
- "price_micro_usd": {
- "type": "integer"
- },
- "price_usd": {
- "type": "number"
- },
- "quote_id": {
- "type": "string"
- },
- "results": {
- "description": "Paid rows, after step 2.",
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "status": {
- "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
- "enum": [
- "quote",
- "nothing_billable",
- "ok"
- ],
- "type": "string"
- },
- "statuses": {
- "description": "Status of every domain, free.",
- "items": {
- "type": "object"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "status"
-]get_company_hiring_intent5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "linear.app"
-]New value: +[
+ "ramp.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "ats_type": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "buying_signals": {
+ "properties": {
+ "cloud_infra": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "data_ai": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "databases": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "observability": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "sales_tools": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "confidence": {
+ "description": "high: the company website links to the board. unverified: only the board name matches the domain.",
+ "enum": [
+ "high",
+ "unverified",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "department_breakdown": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "function_breakdown": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "hiring_status": {
+ "enum": [
+ "hypergrowth",
+ "active_hiring",
+ "steady"
+ ],
+ "type": "string"
+ },
+ "intent_score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "jobs_truncated": {
+ "type": "boolean"
+ },
+ "next_steps": {
+ "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
+ "items": {
+ "properties": {
+ "body": {
+ "type": "object"
+ },
+ "mcp_tool": {
+ "type": "string"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "why": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "notable_open_roles": {
+ "items": {
+ "type": "object"
+ },
+ "maxItems": 10,
+ "type": "array"
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "remote_roles": {
+ "type": "integer"
+ },
+ "roles_posted_last_30_days": {
+ "type": "integer"
+ },
+ "roles_with_known_post_date": {
+ "type": "integer"
+ },
+ "status": {
+ "description": "Only ok is charged.",
+ "enum": [
+ "ok",
+ "no_open_jobs",
+ "unreachable",
+ "not_found"
+ ],
+ "type": "string"
+ },
+ "top_demanded_technologies": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "top_locations": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "total_open_roles": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "checked_at"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "ats_type": {
- "type": [
- "string",
- "null"
- ]
- },
- "buying_signals": {
- "properties": {
- "cloud_infra": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "data_ai": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "databases": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "observability": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "sales_tools": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "type": "object"
- },
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "confidence": {
- "description": "high: the company website links to the board. unverified: only the board name matches the domain.",
- "enum": [
- "high",
- "unverified",
- null
- ],
- "type": [
- "string",
- "null"
- ]
- },
- "department_breakdown": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "domain": {
- "type": "string"
- },
- "function_breakdown": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "hiring_status": {
- "enum": [
- "hypergrowth",
- "active_hiring",
- "steady"
- ],
- "type": "string"
- },
- "intent_score": {
- "maximum": 100,
- "minimum": 0,
- "type": "integer"
- },
- "jobs_truncated": {
- "type": "boolean"
- },
- "next_steps": {
- "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
- "items": {
- "properties": {
- "body": {
- "type": "object"
- },
- "mcp_tool": {
- "type": "string"
- },
- "price_usd": {
- "type": "number"
- },
- "tool": {
- "type": "string"
- },
- "url": {
- "type": "string"
- },
- "why": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "notable_open_roles": {
- "items": {
- "type": "object"
- },
- "maxItems": 10,
- "type": "array"
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "remote_roles": {
- "type": "integer"
- },
- "roles_posted_last_30_days": {
- "type": "integer"
- },
- "roles_with_known_post_date": {
- "type": "integer"
- },
- "status": {
- "description": "Only ok is charged.",
- "enum": [
- "ok",
- "no_open_jobs",
- "unreachable",
- "not_found"
- ],
- "type": "string"
- },
- "top_demanded_technologies": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "top_locations": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "total_open_roles": {
- "type": "integer"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "checked_at"
-]get_company_open_jobs5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "notion.so"
+]Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "ats_type": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "board_match": {
+ "description": "name_match: the board name equals the first part of the domain, so check generic names.",
+ "enum": [
+ "name_match",
+ "careers_page_link",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "board_slug": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "confidence": {
+ "description": "high: the company website links to this board. unverified: only the board name matches the domain name.",
+ "enum": [
+ "high",
+ "unverified",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "diff": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "domain": {
+ "type": "string"
+ },
+ "jobs": {
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "jobs_by_department": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "jobs_returned": {
+ "type": "integer"
+ },
+ "jobs_truncated": {
+ "type": "boolean"
+ },
+ "jobs_with_salary": {
+ "type": "integer"
+ },
+ "next_poll_after": {
+ "description": "Job boards change slowly; calling again before this time is usually wasted.",
+ "format": "date-time",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "next_steps": {
+ "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
+ "items": {
+ "properties": {
+ "body": {
+ "type": "object"
+ },
+ "mcp_tool": {
+ "type": "string"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "why": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "remote_jobs": {
+ "type": "integer"
+ },
+ "status": {
+ "description": "Only ok is charged.",
+ "enum": [
+ "ok",
+ "no_open_jobs",
+ "unreachable",
+ "not_found"
+ ],
+ "type": "string"
+ },
+ "top_locations": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "top_technologies": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "total_active_jobs": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "jobs",
+ "checked_at"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "ats_type": {
- "type": [
- "string",
- "null"
- ]
- },
- "board_match": {
- "description": "name_match: the board name equals the first part of the domain, so check generic names.",
- "enum": [
- "name_match",
- "careers_page_link",
- null
- ],
- "type": [
- "string",
- "null"
- ]
- },
- "board_slug": {
- "type": [
- "string",
- "null"
- ]
- },
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "confidence": {
- "description": "high: the company website links to this board. unverified: only the board name matches the domain name.",
- "enum": [
- "high",
- "unverified",
- null
- ],
- "type": [
- "string",
- "null"
- ]
- },
- "diff": {
- "type": [
- "object",
- "null"
- ]
- },
- "domain": {
- "type": "string"
- },
- "jobs": {
- "items": {
- "type": "object"
- },
- "type": "array"
- },
- "jobs_by_department": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "jobs_returned": {
- "type": "integer"
- },
- "jobs_truncated": {
- "type": "boolean"
- },
- "jobs_with_salary": {
- "type": "integer"
- },
- "next_poll_after": {
- "description": "Job boards change slowly; calling again before this time is usually wasted.",
- "format": "date-time",
- "type": [
- "string",
- "null"
- ]
- },
- "next_steps": {
- "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
- "items": {
- "properties": {
- "body": {
- "type": "object"
- },
- "mcp_tool": {
- "type": "string"
- },
- "price_usd": {
- "type": "number"
- },
- "tool": {
- "type": "string"
- },
- "url": {
- "type": "string"
- },
- "why": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "remote_jobs": {
- "type": "integer"
- },
- "status": {
- "description": "Only ok is charged.",
- "enum": [
- "ok",
- "no_open_jobs",
- "unreachable",
- "not_found"
- ],
- "type": "string"
- },
- "top_locations": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "top_technologies": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "total_active_jobs": {
- "type": "integer"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "jobs",
- "checked_at"
-]get_company_profile4 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "breakout_summary": {
+ "description": "get_company_profile only. Growth estimate from public signals (hiring, Google Ads, site maturity); not investment advice.",
+ "properties": {
+ "method": {
+ "type": "string"
+ },
+ "reasons": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "signal": {
+ "enum": [
+ "strong",
+ "moderate",
+ "weak",
+ "none",
+ "insufficient_data"
+ ],
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "contacts": {
+ "description": "get_company_profile only. Same fields as extract_company_contacts.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "domain": {
+ "type": "string"
+ },
+ "footprint": {
+ "description": "found, not_found or unknown for each public signal.",
+ "properties": {
+ "google_ads": {
+ "type": "string"
+ },
+ "job_board_with_open_roles": {
+ "type": "string"
+ },
+ "website_ad_or_analytics_tags": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "google_ads": {
+ "description": "Same fields as get_google_ads_by_domain.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "hiring_intent": {
+ "description": "Same fields as get_company_hiring_intent.",
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sections_status": {
+ "additionalProperties": {
+ "type": "string"
+ },
+ "type": "object"
+ },
+ "sections_with_data": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "signals": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Only ok is charged: at least two sections have data (of four for get_company_profile, three for company_footprint_check).",
+ "enum": [
+ "ok",
+ "insufficient_data"
+ ],
+ "type": "string"
+ },
+ "tech_stack": {
+ "description": "Same fields as detect_website_tech_stack.",
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "sections_status",
+ "checked_at"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "domain": {
- "type": "string"
- },
- "footprint": {
- "description": "found, not_found or unknown for each public signal.",
- "properties": {
- "google_ads": {
- "type": "string"
- },
- "job_board_with_open_roles": {
- "type": "string"
- },
- "website_ad_or_analytics_tags": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "google_ads": {
- "description": "Same fields as get_google_ads_by_domain.",
- "type": [
- "object",
- "null"
- ]
- },
- "hiring_intent": {
- "description": "Same fields as get_company_hiring_intent.",
- "type": [
- "object",
- "null"
- ]
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "sections_status": {
- "additionalProperties": {
- "type": "string"
- },
- "type": "object"
- },
- "sections_with_data": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "signals": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "status": {
- "description": "Only ok is charged: at least two of the three sections have data.",
- "enum": [
- "ok",
- "insufficient_data"
- ],
- "type": "string"
- },
- "tech_stack": {
- "description": "Same fields as detect_website_tech_stack.",
- "type": [
- "object",
- "null"
- ]
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "sections_status",
- "checked_at"
-]get_email_codeget_google_ads_by_domain4 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "ads": {
+ "items": {
+ "properties": {
+ "advertiser_id": {
+ "type": "string"
+ },
+ "advertiser_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "creative_id": {
+ "type": "string"
+ },
+ "first_shown": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "format": {
+ "type": "string"
+ },
+ "last_shown": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "preview_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "transparency_url": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "maxItems": 40,
+ "type": "array"
+ },
+ "ads_returned": {
+ "type": "integer"
+ },
+ "ads_shown_last_30_days_in_sample": {
+ "type": "integer"
+ },
+ "advertisers": {
+ "items": {
+ "properties": {
+ "ads_in_sample": {
+ "type": "integer"
+ },
+ "advertiser_id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "checked_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "earliest_first_shown_in_sample": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "formats_in_sample": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "latest_last_shown_in_sample": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "next_steps": {
+ "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
+ "items": {
+ "properties": {
+ "body": {
+ "type": "object"
+ },
+ "mcp_tool": {
+ "type": "string"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "why": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "note": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "region": {
+ "type": "string"
+ },
+ "status": {
+ "description": "Only ok is charged.",
+ "enum": [
+ "ok",
+ "no_ads"
+ ],
+ "type": "string"
+ },
+ "total_ads_estimate": {
+ "properties": {
+ "high": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "low": {
+ "type": "integer"
+ }
+ },
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain",
+ "status",
+ "checked_at"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "ads": {
- "items": {
- "properties": {
- "advertiser_id": {
- "type": "string"
- },
- "advertiser_name": {
- "type": [
- "string",
- "null"
- ]
- },
- "creative_id": {
- "type": "string"
- },
- "first_shown": {
- "type": [
- "string",
- "null"
- ]
- },
- "format": {
- "type": "string"
- },
- "last_shown": {
- "type": [
- "string",
- "null"
- ]
- },
- "preview_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "transparency_url": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "maxItems": 40,
- "type": "array"
- },
- "ads_returned": {
- "type": "integer"
- },
- "ads_shown_last_30_days_in_sample": {
- "type": "integer"
- },
- "advertisers": {
- "items": {
- "properties": {
- "ads_in_sample": {
- "type": "integer"
- },
- "advertiser_id": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "checked_at": {
- "format": "date-time",
- "type": "string"
- },
- "domain": {
- "type": "string"
- },
- "earliest_first_shown_in_sample": {
- "type": [
- "string",
- "null"
- ]
- },
- "formats_in_sample": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "latest_last_shown_in_sample": {
- "type": [
- "string",
- "null"
- ]
- },
- "next_steps": {
- "description": "Suggested follow-up calls on the same domain, with the exact body. Optional to use.",
- "items": {
- "properties": {
- "body": {
- "type": "object"
- },
- "mcp_tool": {
- "type": "string"
- },
- "price_usd": {
- "type": "number"
- },
- "tool": {
- "type": "string"
- },
- "url": {
- "type": "string"
- },
- "why": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "note": {
- "type": [
- "string",
- "null"
- ]
- },
- "region": {
- "type": "string"
- },
- "status": {
- "description": "Only ok is charged.",
- "enum": [
- "ok",
- "no_ads"
- ],
- "type": "string"
- },
- "total_ads_estimate": {
- "properties": {
- "high": {
- "type": [
- "integer",
- "null"
- ]
- },
- "low": {
- "type": "integer"
- }
- },
- "type": [
- "object",
- "null"
- ]
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status",
- "checked_at"
-]list_email_messagesmuse_agentic_store_readiness_auditor6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "bot_access": {
+ "additionalProperties": {
+ "properties": {
+ "home_allowed": {
+ "type": "boolean"
+ },
+ "sample_product_allowed": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "home_allowed",
+ "sample_product_allowed"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "discovery": {
+ "additionalProperties": {
+ "properties": {
+ "http_status": {
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "valid": {
+ "type": "boolean"
+ },
+ "validation": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "http_status",
+ "valid",
+ "validation"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "fixes": {
+ "items": {
+ "properties": {
+ "action": {
+ "type": "string"
+ },
+ "check": {
+ "type": "string"
+ },
+ "priority": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "priority",
+ "check",
+ "action"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "payment_hints": {
+ "properties": {
+ "paypal": {
+ "type": "boolean"
+ },
+ "shop_pay": {
+ "type": "boolean"
+ },
+ "stripe_link": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "stripe_link",
+ "shop_pay",
+ "paypal"
+ ],
+ "type": "object"
+ },
+ "product": {
+ "properties": {
+ "agentic_checkout_supported": {
+ "properties": {
+ "paypal": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "shop_pay": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "stripe_link": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "ucp": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "ucp",
+ "stripe_link",
+ "shop_pay",
+ "paypal"
+ ],
+ "type": "object"
+ },
+ "aggregate_rating": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "brand": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "checkout_hints": {
+ "properties": {
+ "paypal": {
+ "type": "boolean"
+ },
+ "shop_pay": {
+ "type": "boolean"
+ },
+ "stripe_link": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "stripe_link",
+ "shop_pay",
+ "paypal"
+ ],
+ "type": "object"
+ },
+ "currency": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "extraction_source": {
+ "type": "string"
+ },
+ "in_stock": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "price": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "return_policy": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "review_count": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "shipping_summary": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "structured_fields": {
+ "properties": {
+ "aggregateRating": {
+ "type": "boolean"
+ },
+ "availability": {
+ "type": "boolean"
+ },
+ "hasMerchantReturnPolicy": {
+ "type": "boolean"
+ },
+ "offers": {
+ "type": "boolean"
+ },
+ "price": {
+ "type": "boolean"
+ },
+ "product_json_ld": {
+ "type": "boolean"
+ },
+ "shippingDetails": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "product_json_ld",
+ "offers",
+ "price",
+ "availability",
+ "shippingDetails",
+ "hasMerchantReturnPolicy",
+ "aggregateRating"
+ ],
+ "type": "object"
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": "string"
+ },
+ "variants": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "url",
+ "title",
+ "brand",
+ "price",
+ "currency",
+ "in_stock",
+ "variants",
+ "aggregate_rating",
+ "review_count",
+ "shipping_summary",
+ "return_policy",
+ "agentic_checkout_supported",
+ "checkout_hints",
+ "structured_fields",
+ "extraction_source",
+ "limitations"
+ ],
+ "type": "object"
+ },
+ "readiness_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "sample_product_url": {
+ "type": "string"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "bot_access": {
- "additionalProperties": {
- "properties": {
- "home_allowed": {
- "type": "boolean"
- },
- "sample_product_allowed": {
- "type": "boolean"
- }
- },
- "required": [
- "home_allowed",
- "sample_product_allowed"
- ],
- "type": "object"
- },
- "type": "object"
- },
- "discovery": {
- "additionalProperties": {
- "properties": {
- "http_status": {
- "type": [
- "integer",
- "null"
- ]
- },
- "valid": {
- "type": "boolean"
- },
- "validation": {
- "type": "string"
- }
- },
- "required": [
- "http_status",
- "valid",
- "validation"
- ],
- "type": "object"
- },
- "type": "object"
- },
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "fixes": {
- "items": {
- "properties": {
- "action": {
- "type": "string"
- },
- "check": {
- "type": "string"
- },
- "priority": {
- "type": "integer"
- }
- },
- "required": [
- "priority",
- "check",
- "action"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "payment_hints": {
- "properties": {
- "paypal": {
- "type": "boolean"
- },
- "shop_pay": {
- "type": "boolean"
- },
- "stripe_link": {
- "type": "boolean"
- }
- },
- "required": [
- "stripe_link",
- "shop_pay",
- "paypal"
- ],
- "type": "object"
- },
- "product": {
- "properties": {
- "agentic_checkout_supported": {
- "properties": {
- "paypal": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "shop_pay": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "stripe_link": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "ucp": {
- "type": [
- "boolean",
- "null"
- ]
- }
- },
- "required": [
- "ucp",
- "stripe_link",
- "shop_pay",
- "paypal"
- ],
- "type": "object"
- },
- "aggregate_rating": {
- "type": [
- "number",
- "null"
- ]
- },
- "brand": {
- "type": [
- "string",
- "null"
- ]
- },
- "checkout_hints": {
- "properties": {
- "paypal": {
- "type": "boolean"
- },
- "shop_pay": {
- "type": "boolean"
- },
- "stripe_link": {
- "type": "boolean"
- }
- },
- "required": [
- "stripe_link",
- "shop_pay",
- "paypal"
- ],
- "type": "object"
- },
- "currency": {
- "type": [
- "string",
- "null"
- ]
- },
- "extraction_source": {
- "type": "string"
- },
- "in_stock": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "price": {
- "type": [
- "number",
- "null"
- ]
- },
- "return_policy": {
- "type": [
- "string",
- "null"
- ]
- },
- "review_count": {
- "type": [
- "number",
- "null"
- ]
- },
- "shipping_summary": {
- "type": [
- "string",
- "null"
- ]
- },
- "structured_fields": {
- "properties": {
- "aggregateRating": {
- "type": "boolean"
- },
- "availability": {
- "type": "boolean"
- },
- "hasMerchantReturnPolicy": {
- "type": "boolean"
- },
- "offers": {
- "type": "boolean"
- },
- "price": {
- "type": "boolean"
- },
- "product_json_ld": {
- "type": "boolean"
- },
- "shippingDetails": {
- "type": "boolean"
- }
- },
- "required": [
- "product_json_ld",
- "offers",
- "price",
- "availability",
- "shippingDetails",
- "hasMerchantReturnPolicy",
- "aggregateRating"
- ],
- "type": "object"
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "url": {
- "type": "string"
- },
- "variants": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "required": [
- "url",
- "title",
- "brand",
- "price",
- "currency",
- "in_stock",
- "variants",
- "aggregate_rating",
- "review_count",
- "shipping_summary",
- "return_policy",
- "agentic_checkout_supported",
- "checkout_hints",
- "structured_fields",
- "extraction_source",
- "limitations"
- ],
- "type": "object"
- },
- "readiness_score": {
- "type": [
- "number",
- "null"
- ]
- },
- "sample_product_url": {
- "type": "string"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]muse_conversion_leak_lead_finder6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "active_ad_spend_verified": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "candidate": {
+ "type": "boolean"
+ },
+ "decision_maker_verified": {
+ "type": "boolean"
+ },
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "public_contacts": {
+ "type": "object"
+ },
+ "readiness": {
+ "type": "object"
+ },
+ "seo_traffic_verified": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "active_ad_spend_verified": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "candidate": {
- "type": "boolean"
- },
- "decision_maker_verified": {
- "type": "boolean"
- },
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "public_contacts": {
- "type": "object"
- },
- "readiness": {
- "type": "object"
- },
- "seo_traffic_verified": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]pre_purchase_merchant_trust_check8 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Input schema / properties / merchant_wallet_or_id / descriptionAdded value: +"Optional merchant identifier as context; supplying a wallet does not establish ownership or on-chain reputation."Input schema / properties / transaction_amount_usd / descriptionAdded value: +"Optional intended purchase value in USD as context; it does not authorize a purchase or change the scan price."Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "latency_ms": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "recommendation": {
+ "type": "string"
+ },
+ "risk_level": {
+ "enum": [
+ "LOW",
+ "MEDIUM",
+ "HIGH",
+ "CRITICAL"
+ ],
+ "type": "string"
+ },
+ "safe_to_buy": {
+ "type": "boolean"
+ },
+ "signals": {
+ "properties": {
+ "active_ad_campaigns": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "domain_age_days": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "has_active_employees": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "legitimate_tech_stack": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "onchain_reputation_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "open_jobs_count": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain_age_days",
+ "has_active_employees",
+ "open_jobs_count",
+ "legitimate_tech_stack",
+ "active_ad_campaigns",
+ "onchain_reputation_score"
+ ],
+ "type": "object"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ },
+ "trust_score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": "number"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "latency_ms": {
- "minimum": 0,
- "type": "integer"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "recommendation": {
- "type": "string"
- },
- "risk_level": {
- "enum": [
- "LOW",
- "MEDIUM",
- "HIGH",
- "CRITICAL"
- ],
- "type": "string"
- },
- "safe_to_buy": {
- "type": "boolean"
- },
- "signals": {
- "properties": {
- "active_ad_campaigns": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "domain_age_days": {
- "type": [
- "number",
- "null"
- ]
- },
- "has_active_employees": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "legitimate_tech_stack": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "onchain_reputation_score": {
- "type": [
- "number",
- "null"
- ]
- },
- "open_jobs_count": {
- "type": [
- "number",
- "null"
- ]
- }
- },
- "required": [
- "domain_age_days",
- "has_active_employees",
- "open_jobs_count",
- "legitimate_tech_stack",
- "active_ad_campaigns",
- "onchain_reputation_score"
- ],
- "type": "object"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- },
- "trust_score": {
- "maximum": 100,
- "minimum": 0,
- "type": "number"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]private_blind_lookup5 fields changedInput schema / properties / target / descriptionAdded value: +"Bare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination."Input schema / properties / tool / descriptionAdded value: +"Lookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "privacy_guarantee": {
+ "type": "string"
+ },
+ "result": {
+ "type": "object"
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "privacy_guarantee": {
- "type": "string"
- },
- "result": {
- "type": "object"
- },
- "status": {
- "type": "string"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]universal_product_url_to_json6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / product_url / descriptionAdded value: +"Public HTTP(S) product detail URL to extract structured product evidence from; use a product page rather than a store homepage."Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "agentic_checkout_supported": {
+ "properties": {
+ "paypal": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "shop_pay": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "stripe_link": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "ucp": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "ucp",
+ "stripe_link",
+ "shop_pay",
+ "paypal"
+ ],
+ "type": "object"
+ },
+ "aggregate_rating": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "brand": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "checkout_hints": {
+ "properties": {
+ "paypal": {
+ "type": "boolean"
+ },
+ "shop_pay": {
+ "type": "boolean"
+ },
+ "stripe_link": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "stripe_link",
+ "shop_pay",
+ "paypal"
+ ],
+ "type": "object"
+ },
+ "currency": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "extraction_source": {
+ "type": "string"
+ },
+ "in_stock": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "price": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "return_policy": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "review_count": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "shipping_summary": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ },
+ "structured_fields": {
+ "properties": {
+ "aggregateRating": {
+ "type": "boolean"
+ },
+ "availability": {
+ "type": "boolean"
+ },
+ "hasMerchantReturnPolicy": {
+ "type": "boolean"
+ },
+ "offers": {
+ "type": "boolean"
+ },
+ "price": {
+ "type": "boolean"
+ },
+ "product_json_ld": {
+ "type": "boolean"
+ },
+ "shippingDetails": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "product_json_ld",
+ "offers",
+ "price",
+ "availability",
+ "shippingDetails",
+ "hasMerchantReturnPolicy",
+ "aggregateRating"
+ ],
+ "type": "object"
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": "string"
+ },
+ "variants": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "agentic_checkout_supported": {
- "properties": {
- "paypal": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "shop_pay": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "stripe_link": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "ucp": {
- "type": [
- "boolean",
- "null"
- ]
- }
- },
- "required": [
- "ucp",
- "stripe_link",
- "shop_pay",
- "paypal"
- ],
- "type": "object"
- },
- "aggregate_rating": {
- "type": [
- "number",
- "null"
- ]
- },
- "brand": {
- "type": [
- "string",
- "null"
- ]
- },
- "checkout_hints": {
- "properties": {
- "paypal": {
- "type": "boolean"
- },
- "shop_pay": {
- "type": "boolean"
- },
- "stripe_link": {
- "type": "boolean"
- }
- },
- "required": [
- "stripe_link",
- "shop_pay",
- "paypal"
- ],
- "type": "object"
- },
- "currency": {
- "type": [
- "string",
- "null"
- ]
- },
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "extraction_source": {
- "type": "string"
- },
- "in_stock": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "price": {
- "type": [
- "number",
- "null"
- ]
- },
- "return_policy": {
- "type": [
- "string",
- "null"
- ]
- },
- "review_count": {
- "type": [
- "number",
- "null"
- ]
- },
- "shipping_summary": {
- "type": [
- "string",
- "null"
- ]
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- },
- "structured_fields": {
- "properties": {
- "aggregateRating": {
- "type": "boolean"
- },
- "availability": {
- "type": "boolean"
- },
- "hasMerchantReturnPolicy": {
- "type": "boolean"
- },
- "offers": {
- "type": "boolean"
- },
- "price": {
- "type": "boolean"
- },
- "product_json_ld": {
- "type": "boolean"
- },
- "shippingDetails": {
- "type": "boolean"
- }
- },
- "required": [
- "product_json_ld",
- "offers",
- "price",
- "availability",
- "shippingDetails",
- "hasMerchantReturnPolicy",
- "aggregateRating"
- ],
- "type": "object"
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "url": {
- "type": "string"
- },
- "variants": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]url_to_clean_markdown6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / max_chars / descriptionAdded value: +"Maximum characters of Markdown to return; longer pages are truncated and marked as such."Input schema / properties / url / descriptionAdded value: +"Public HTTP(S) page URL to convert to Markdown; private addresses, unsafe redirects and credential-bearing URLs are rejected."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "markdown": {
+ "type": "string"
+ },
+ "meta_description": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "token_count_estimate": {
+ "type": "integer"
+ },
+ "truncated": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "markdown": {
- "type": "string"
- },
- "meta_description": {
- "type": "string"
- },
- "status": {
- "type": "string"
- },
- "title": {
- "type": "string"
- },
- "token_count_estimate": {
- "type": "integer"
- },
- "truncated": {
- "type": "boolean"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]verified_merchant_json_badge6 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / domain / examplesPrevious value: -[
- "example.com"
-]New value: +[
+ "allbirds.com"
+]Output schema / anyOfAdded value: +[
+ {
+ "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "error_reason": {
+ "type": "string"
+ },
+ "latency_ms": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "limitations": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "organization": {
+ "type": "object"
+ },
+ "recommendation": {
+ "type": "string"
+ },
+ "risk_level": {
+ "enum": [
+ "LOW",
+ "MEDIUM",
+ "HIGH",
+ "CRITICAL"
+ ],
+ "type": "string"
+ },
+ "safe_to_buy": {
+ "type": "boolean"
+ },
+ "signals": {
+ "properties": {
+ "active_ad_campaigns": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "domain_age_days": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "has_active_employees": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "legitimate_tech_stack": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "onchain_reputation_score": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "open_jobs_count": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "domain_age_days",
+ "has_active_employees",
+ "open_jobs_count",
+ "legitimate_tech_stack",
+ "active_ad_campaigns",
+ "onchain_reputation_score"
+ ],
+ "type": "object"
+ },
+ "signed_statement": {
+ "type": "string"
+ },
+ "status": {
+ "enum": [
+ "ok",
+ "no_data",
+ "unreachable"
+ ],
+ "type": "string"
+ },
+ "trust_score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": "number"
+ },
+ "verification_key": {
+ "type": "object"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / descriptionRemoved value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "error_reason": {
- "type": "string"
- },
- "latency_ms": {
- "minimum": 0,
- "type": "integer"
- },
- "limitations": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "organization": {
- "type": "object"
- },
- "recommendation": {
- "type": "string"
- },
- "risk_level": {
- "enum": [
- "LOW",
- "MEDIUM",
- "HIGH",
- "CRITICAL"
- ],
- "type": "string"
- },
- "safe_to_buy": {
- "type": "boolean"
- },
- "signals": {
- "properties": {
- "active_ad_campaigns": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "domain_age_days": {
- "type": [
- "number",
- "null"
- ]
- },
- "has_active_employees": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "legitimate_tech_stack": {
- "type": [
- "boolean",
- "null"
- ]
- },
- "onchain_reputation_score": {
- "type": [
- "number",
- "null"
- ]
- },
- "open_jobs_count": {
- "type": [
- "number",
- "null"
- ]
- }
- },
- "required": [
- "domain_age_days",
- "has_active_employees",
- "open_jobs_count",
- "legitimate_tech_stack",
- "active_ad_campaigns",
- "onchain_reputation_score"
- ],
- "type": "object"
- },
- "signed_statement": {
- "type": "string"
- },
- "status": {
- "enum": [
- "ok",
- "no_data",
- "unreachable"
- ],
- "type": "string"
- },
- "trust_score": {
- "maximum": 100,
- "minimum": 0,
- "type": "number"
- },
- "verification_key": {
- "type": "object"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]verify_domain_legitimacy_and_securityx402_merchant_trust_check5 fields changedInput schema / properties / contextAdded value: +{
+ "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+ "type": "string"
+}Input schema / properties / target_url / descriptionAdded value: +"Public HTTPS x402 API endpoint to inspect before signing a payment authorization; this scan does not authorize payment."Output schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "domain": {
+ "type": "string"
+ },
+ "latency_ms": {
+ "type": "number"
+ },
+ "marketplace_reputation": {
+ "description": "Public Coinbase CDP Bazaar statistics for the target host (30 days): listed, unique payers, calls, neutral demand signal.",
+ "type": "object"
+ },
+ "matched_flags": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "prompt_injection_risk": {
+ "enum": [
+ "LOW",
+ "MEDIUM",
+ "CRITICAL"
+ ],
+ "type": "string"
+ },
+ "recommendation": {
+ "type": "string"
+ },
+ "safe_to_pay": {
+ "type": "boolean"
+ },
+ "status": {
+ "type": "string"
+ },
+ "trust_score": {
+ "maximum": 100,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "valid_x402_config": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "domain",
+ "status"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "status": {
+ "maximum": 599,
+ "minimum": 400,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "code"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "domain": {
- "type": "string"
- },
- "latency_ms": {
- "type": "number"
- },
- "matched_flags": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "prompt_injection_risk": {
- "enum": [
- "LOW",
- "MEDIUM",
- "CRITICAL"
- ],
- "type": "string"
- },
- "recommendation": {
- "type": "string"
- },
- "safe_to_pay": {
- "type": "boolean"
- },
- "status": {
- "type": "string"
- },
- "trust_score": {
- "maximum": 100,
- "minimum": 0,
- "type": "integer"
- },
- "valid_x402_config": {
- "type": "boolean"
- }
-}Output schema / requiredRemoved value: -[
- "domain",
- "status"
-]v0.1.000_ask_hirepulse_advisoragentic_shelf_schema_comparatorask_hirepulse_advisorb2b_vendor_stability_evaluatorbatch_lookupcheckout_active_promo_code_findercompany_footprint_checkdetect_website_tech_stackextract_company_contactsfind_hot_buyersget_company_hiring_intentget_company_open_jobsget_company_profileget_google_ads_by_domainmuse_agentic_store_readiness_auditormuse_conversion_leak_lead_finderpre_purchase_merchant_trust_checkprivate_blind_lookupuniversal_product_url_to_jsonurl_to_clean_markdownverified_merchant_json_badgeverify_domain_legitimacy_and_securityx402_merchant_trust_checkScored across 26 tools
The set is split into recognizable clusters (company intelligence, merchant/e-commerce trust, x402 endpoint checks, temp-email testing), and most descriptions explicitly say which sibling tool to use instead, which sharply reduces misselection (e.g. get_company_hiring_intent vs get_company_open_jobs vs get_company_profile). Residual overlap remains between the near-identical company-research tools and among the merchant-trust variants (pre_purchase, x402, badge, b2b_vendor_stability), where an agent must read carefully to choose.
All names are snake_case and readable, but the shape is mixed: verb-first tools (get_company_profile, detect_website_tech_stack, list_email_messages, extract_company_contacts) coexist with noun-first labels (universal_product_url_to_json, agentic_shelf_schema_comparator, b2b_vendor_stability_evaluator, verified_merchant_json_badge, company_footprint_check, private_blind_lookup). Brand prefixes like muse_ and x402_ add a second naming convention within the same list.
26 tools is heavy for a single server and sits at the top of the acceptable band; the surface spans four loosely related business areas rather than one tight domain. Each tool does have a distinct output, so it is not padding, but the breadth makes it hard to hold the whole set in mind.
Coverage per sub-domain is strong: company research has profile, jobs, hiring intent, ads, tech stack, contacts, footprint, batching and ranking; merchant trust has consumer, x402, vendor and signed-badge variants; the inbox has a full create/list/extract/delete lifecycle. Only minor gaps exist, such as no quote/settlement-status tool despite the multi-step quote_id flows and no update-style operations.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Remote MCP server that gives Claude, ChatGPT, Cursor or any MCP client Google search volume, CPC, competition and similar keywords for 50+ countries. Works with no signup at 20 lookups a day; sign in with OAuth or an API key for higher limits, or $4.99 a month for unlimited.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Production-grade MCP gateway delivering 8 real-time AI tools with instant x402 micropayments settled in USDC on Base Mainnet or SPL-USDC on Solana. Features Basescan contract auditing, wallet analytics, headless browser scraping, and pre-scraped oracle data feeds.
