New-Location Expansion Signal Detector
Catch a brand opening in a new metro weeks early by reading its local hiring cluster and Maps footprint
https://apidirect.io/mcp?token=YOUR_API_KEY
Tell me if {brand} is about to open a location in {target_metro} based on their LinkedIn hiring and Google Maps footprint
new-location-expansion-signal-detector.
Any agent can also call get_skill(skill_id="new-location-expansion-signal-detector") to pull these steps on demand.
What it does
Brands staff a new location weeks before opening. A cluster of metro-specific operational job posts on LinkedIn is the earliest public signal, and a Maps cross-check confirms whether the storefront is already listed, so you can reach them before the doors open.
Who it's for: Suppliers, commercial realtors, and vendors who want first contact
Inputs
| Input | Required | Description | Example |
|---|---|---|---|
brand |
Yes | The company you suspect is expanding | Sweetgreen |
target_metro |
Yes | The metro you want expansion signals for | Miami, Florida |
How your agent runs it
-
1
search_linkedin_companies(query="{brand}")Resolve the brand to its numeric company_id so job results are scoped to the real employer.
-
2
search_linkedin_jobs(query="{brand} {target_metro}", company_ids=<company_id>, posted_ago=7d, sort_by=most_recent)Surface brand-new postings in the metro; a cluster of local ops roles (GM, store/shift manager) is the expansion signal.
-
3
linkedin_job_details(url=<job_url>)Open each posting to confirm the work location and read the role; multiple local operational roles equals a confirmed buildout.
-
4
search_places(query="{brand} {target_metro}", pages=2)Cross-check Google Maps for a recently added or not-yet-open {brand} location to time outreach precisely.
Tools used
The full playbook
This is exactly what the MCP returns to your agent (via the new-location-expansion-signal-detector prompt or get_skill tool), with your inputs filled in.
SKILL: New-Location Expansion Signal Detector
Brands staff a new location weeks before opening. A cluster of metro-specific operational job posts on LinkedIn is the earliest public signal, and a Maps cross-check confirms whether the storefront is already listed, so you can reach them before the doors open.
You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.
INPUTS:
- brand (required): <brand — ASK THE USER>
- target_metro (required): <target_metro — ASK THE USER>
STEPS:
1. Tool `search_linkedin_companies` — search_linkedin_companies(query="<brand>")
Resolve the brand to its numeric company_id so job results are scoped to the real employer.
2. Tool `search_linkedin_jobs` — search_linkedin_jobs(query="<brand> <target_metro>", company_ids=<company_id>, posted_ago=7d, sort_by=most_recent)
Surface brand-new postings in the metro; a cluster of local ops roles (GM, store/shift manager) is the expansion signal.
3. Tool `linkedin_job_details` — linkedin_job_details(url=<job_url>)
Open each posting to confirm the work location and read the role; multiple local operational roles equals a confirmed buildout.
4. Tool `search_places` — search_places(query="<brand> <target_metro>", pages=2)
Cross-check Google Maps for a recently added or not-yet-open <brand> location to time outreach precisely.
DELIVER: An early-warning brief on <brand> opening in <target_metro>, with the hiring cluster, role details, and Maps footprint to pitch before launch
Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.