create_signal
Create a signal: the account checks one thing on LinkedIn on a schedule and records every new item it finds as an event, which you read with get_signal_events. The first check records a silent baseline: what is already there is not reported, except that personPosts, companyPosts and postSearch signals report posts published since the signal was created. Creating a signal that already exists on the account (same type and target) returns that signal instead of a second one; a paused one stays paused. Pass only the target fields of the chosen type:
network: no target. Reports connectionAccepted, connectionAdded and connectionRequestReceived. Checked every hour; spends nothing from account limits.
profileViewers: no target. Reports profileViewed. Checked every 3 hours; spends nothing from account limits.
personPosts: personUrl. companyPosts: companyUrl. Reports postPublished. Checked once or twice a day. The first check opens the profile or company page once (1 of stPersonProfileViews or stCompanyPageViews, and the person may see the account among their profile viewers); later checks mostly run as LinkedIn searches and spend some stSearchQueries – usually a few a day for the whole account – plus occasional visits.
postSearch: term (1 to 3 phrases) and an optional filter. Reports postFound for new posts matching any phrase. Checked once or twice a day; each check spends 1 of stSearchQueries. By default an account has 300 searches a month and each postSearch signal spends 30 to 60 of them, so put the wordings of one topic into one signal rather than a signal per phrase.
postEngagement: postUrl, or myPosts: true for the posts the account publishes. Reports commentAdded and reactionAdded. Spends nothing from account limits, apart from occasional visits. A postUrl signal watches the post for 30 days, then stops. Fails with signalLimitReached when the account already has the maximum number of active signals of this type: pause or delete one first.
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": {
"type": "<type>"
},
"name": "create_signal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | postSearch only, required there. 1 to 3 phrases, each up to 50 characters and with no quotation marks inside; a single phrase is a one-item array. Each phrase is searched as an exact phrase, and a post containing any of them is reported. | |
| type | Yes | What to watch: network, profileViewers, personPosts, companyPosts, postSearch or postEngagement. | |
| label | No | Optional. Your own identifier, up to 64 characters, such as a CRM record ID. It comes back with the signal and with every event it produces. | |
| filter | No | postSearch only, optional. Narrows the search; a post must match every field you set. The signal always looks for the newest posts, so there is no sort or date filter. | |
| myPosts | No | postEngagement only. true to watch comments and reactions on the account's own posts. Pass postUrl or myPosts, not both. | |
| postUrl | No | postEngagement only. URL of the post whose new comments and reactions to report. Pass postUrl or myPosts, not both. | |
| personUrl | No | personPosts only, required there. LinkedIn profile URL of the person (e.g., 'https://www.linkedin.com/in/john-doe'). | |
| companyUrl | No | companyPosts only, required there. LinkedIn company page URL (e.g., 'https://www.linkedin.com/company/example'). |