Skip to main content
Glama
Funding & Press Signal Scanner MCP Server

Funding & Press Signal Scanner MCP Server

Get Funding and Press Signals

get_funding_press_signals
Read-onlyIdempotent

Find outbound triggers or qualify accounts by scanning Google News and PR wires for funding rounds, executive moves, product launches, and acquisitions.

Instructions

Scan Google News and PR wires for funding rounds, executive moves, product launches, and acquisitions at any company domain. Returns deduplicated, dated events in flat Clay-ready JSON. Use it to find a trigger for outbound (a fresh raise, a new executive) or to qualify an account before a call. Pass signal_types to report one kind of event, lookback_days to set the window, and domains to scan a list in one call. Requires APIFY_TOKEN; consumes Apify credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "get_funding_press_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain to scan, without https or www, e.g. stripe.com.
domainsNoOptional list of company domains to scan in one run, one row per company. When set and non-empty it overrides domain; still pass the first domain as domain, which the schema requires.
company_nameNoOptional company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.
signal_typesNoReport only these event types. Narrowing narrows the search as well as the answer, so a funding only scan issues one news query instead of four. Omit for every type.
lookback_daysNoHow far back to search, in days. Default 365. Shorten it for trigger based outbound, where a raise from eleven months ago is not a trigger.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domains
      Added value: +{
      +  "description": "Optional list of company domains to scan in one run, one row per company. When set and non-empty it overrides domain; still pass the first domain as domain, which the schema requires.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / lookback_days
      Added value: +{
      +  "description": "How far back to search, in days. Default 365. Shorten it for trigger based outbound, where a raise from eleven months ago is not a trigger.",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / signal_types
      Added value: +{
      +  "description": "Report only these event types. Narrowing narrows the search as well as the answer, so a funding only scan issues one news query instead of four. Omit for every type.",
      +  "items": {
      +    "enum": [
      +      "funding_round",
      +      "ipo",
      +      "acquisition",
      +      "exec_move",
      +      "product_launch",
      +      "partnership"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: output is deduplicated and dated, it requires APIFY_TOKEN, and it consumes Apify credits — auth and cost context the annotations do not carry. Rate limits or failure behavior are still unstated, keeping it 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.

Conciseness4/5

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

Front-loaded with the core verb+resource, then use cases, then parameters. Five sentences, all carrying information. Slightly dense with parentheticals, but no filler sentences.

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

Completeness4/5

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

No output schema exists, and the description compensates by naming the return shape (deduplicated dated events, flat Clay-ready JSON). Auth requirement and cost are disclosed, and every parameter's purpose is touched. Missing only edge-case behavior (empty results, partial failures) for a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the description earns above that by explaining the non-obvious cost/behavior tradeoff of signal_types ('a funding only scan issues one news query instead of four') and the recency reasoning behind lookback_days. It does not add syntax beyond the schema, but it adds decision-relevant meaning.

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

Purpose5/5

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

States a concrete verb and resource set — 'Scan Google News and PR wires for funding rounds, executive moves, product launches, and acquisitions' — and names the specific output ('deduplicated, dated events in flat Clay-ready JSON'). An agent can tell exactly what this does 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.

Usage Guidelines5/5

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

Gives explicit use cases ('find a trigger for outbound (a fresh raise, a new executive)' and 'qualify an account before a call') and even explains the parameter intent ('Shorten it for trigger based outbound, where a raise from eleven months ago is not a trigger'). With no sibling tools, there are no alternatives to exclude, so 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.

Deploy Server

Other Tools