Signals Tools | GTM Tools

signals-tools detects buying-intent signals for a company by domain. Each signal is its own tool, plus an all-in-one detect_signal runner that fans out to every detector. Configurable execution order lets you front-load the cheapest, highest-confidence signals.

Endpoint

https://signals.gtm-engine.sh

Transport	Path
MCP	`/mcp`
REST	`/api/v0/{tool_name}`

Tools

Tool	Tokens	Description
`ping`	0	Health check
`detect_signal`	0	Run all signal detections for a company
`signal_socials_spike`	5	Instagram/TikTok follower spikes
`signal_hiring_role`	5	Hiring for specific roles
`signal_hiring_support`	5	CX/support hiring
`signal_hiring_sales_rep`	5	SDR/BDR hiring
`signal_hiring_sales_leadership`	5	Sales leadership hiring
`signal_hiring_sales_rep_repost`	5	Reposted SDR roles (churn signal)
`signal_trustpilot_negative_reviews`	5	Negative Trustpilot reviews
`signal_trustpilot_negative_support_reviews`	5	Negative support-related reviews
`signal_trustpilot_positive_reviews`	5	Positive Trustpilot reviews
`signal_technologies_identified`	5	Detect tech stack on a website
`set_signals_order`	0	Configure signal execution order
`get_signals_order`	0	View current signal order

detect_signal itself is free — only the individual detectors that fire are charged.

detect_signal (recommended)

Run the full battery for a domain in one call.

Parameter	Type	Required	Description
`domain`	string	Yes	Company domain (e.g. `"gymshark.com"`)
`techs`	string[]	No	Tech identifiers to match (e.g. `["zendesk.com", "intercom.com"]`) — passed to `signal_technologies_identified`

$ curl -X POST https://signals.gtm-engine.sh/api/v0/detect_signal \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"domain": "gymshark.com", "techs": ["zendesk.com", "intercom.com"]}'

1 {
2   "domain": "gymshark.com",
3   "signals": [
4     {
5       "name": "signal_hiring_support",
6       "fired": true,
7       "evidence": [
8         { "title": "CX Team Lead", "url": "https://...", "source": "linkedin" }
9       ]
10     },
11     {
12       "name": "signal_trustpilot_negative_support_reviews",
13       "fired": true,
14       "score": 0.42,
15       "evidence": [
16         { "rating": 1, "snippet": "Terrible support response time...", "url": "https://..." }
17       ]
18     },
19     { "name": "signal_socials_spike", "fired": false }
20   ]
21 }

The execution order is whatever set_signals_order configured (or the default). You can view it with get_signals_order.

Hiring signals

All hiring detectors scan job-board listings and LinkedIn job posts for the target domain.

Tool	Pattern matched
`signal_hiring_role`	Any role given via `role` parameter
`signal_hiring_support`	Customer support / CX titles
`signal_hiring_sales_rep`	SDR / BDR / Account Executive
`signal_hiring_sales_leadership`	VP Sales, Head of Sales, Director of Sales
`signal_hiring_sales_rep_repost`	The same SDR/BDR role posted multiple times — strong churn indicator

Reposted SDR roles are particularly useful for a sales-aid pitch: it means the previous hire didn’t stick, and the team is feeling the pain.

$ curl -X POST https://signals.gtm-engine.sh/api/v0/signal_hiring_role \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"domain": "siena.cx", "role": "Customer Support"}'

Trustpilot signals

Tool	Returns
`signal_trustpilot_negative_reviews`	All recent 1–2 star reviews
`signal_trustpilot_negative_support_reviews`	1–2 star reviews with support keywords (`response`, `agent`, `ticket`, …)
`signal_trustpilot_positive_reviews`	Recent 4–5 star reviews

Negative support reviews are the strongest churn-prevention signal — they let your agent reach out before the customer leaves.

$ curl -X POST https://signals.gtm-engine.sh/api/v0/signal_trustpilot_negative_support_reviews \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"domain": "mammaly.de"}'

signal_socials_spike checks Instagram and TikTok follower counts against a recent baseline. A sustained jump is a marketing-momentum signal.

$ curl -X POST https://signals.gtm-engine.sh/api/v0/signal_socials_spike \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"domain": "gymshark.com"}'

Technology signal

signal_technologies_identified checks the website’s HTML, headers, and tracking scripts for known stack identifiers (e.g. Zendesk, Intercom, Segment, Stripe).

Parameter	Type	Required	Description
`domain`	string	Yes	Company domain
`techs`	string[]	Yes	Identifiers to match (e.g. `["zendesk.com", "intercom.com"]`)

$ curl -X POST https://signals.gtm-engine.sh/api/v0/signal_technologies_identified \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"domain": "siena.cx", "techs": ["zendesk.com", "intercom.com"]}'

1 {
2   "domain": "siena.cx",
3   "matched": ["zendesk.com"],
4   "evidence": [{ "tech": "zendesk.com", "source": "html", "snippet": "..." }]
5 }

Configuring signal order

set_signals_order and get_signals_order let you control which detectors run first when you call detect_signal. Useful for putting the cheapest, highest-precision signals up front so you can short-circuit on the first match.

$ # View current order
$ curl https://signals.gtm-engine.sh/api/v0/get_signals_order \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY"
$ 
$ # Set custom order
$ curl -X POST https://signals.gtm-engine.sh/api/v0/set_signals_order \
>   -H "Authorization: Bearer $GTM_ENGINE_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{
>     "order": [
>       "signal_hiring_sales_rep_repost",
>       "signal_trustpilot_negative_support_reviews",
>       "signal_hiring_support",
>       "signal_socials_spike",
>       "signal_technologies_identified"
>     ]
>   }'

Required environment variables (self-host)

Same as socials-tools:

Variable	Description
`WORKOS_API_KEY`	Auth (production only)
`STRIPE_SECRET_KEY`	Billing (production only)
`WEB_TOOLS_API_KEY`	Required
`WEB_TOOLS_URL`	Required
`RAPIDAPI_LINKEDIN_API_KEY`	Required
`NEXT_PUBLIC_URL`	Required

Next steps

Signal Detection Guide

Stitching detectors into a churn-prevention or expansion workflow.

Signal-Driven Outreach

Agent pattern: signal → company → person → email → message.