com. getcleed/ linkedin-buying-signals
by getcleed.com · remote · no sign-in to list tools · v1.1.0 · published by com.getcleed
Find B2B prospects showing buying signals on LinkedIn and draft the outreach.
15 tools: 2 can delete or cancel things, 8 change things and 5 only read.
Scanned Oct 21, 2026
- Deletes or cancels2Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things8Claude Code: ask: see these tools
- Only reads5Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "find_leads_from_signals" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "find_leads_from_signals" says "find": a word for reading.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
15 tools
Deletes or cancels 2Claude Code: deny
send_emailSend an email to a prospect from the connected mailbox.No findings
Why it is in this group
- The name "send_email" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Send an email to a prospect from the connected mailbox. This reaches a real person immediately and cannot be undone. Pass the subject and body you want sent, or omit them to send the saved draft. Requires a mailbox connected in getcleed under Integrations.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
send_linkedin_messageSend a LinkedIn connection request with a note to a prospect from the connected LinkedIn account.No findings
Why it is in this group
- The name "send_linkedin_message" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account. This reaches a real person immediately and cannot be undone. Pass the note you want sent, or omit it to use the saved draft. Requires LinkedIn connected in getcleed under Integrations.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
Changes things 8Claude Code: ask
add_leads_from_urlsSave LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language).No findings
Why it is in this group
- The name "add_leads_from_urls" says "add": a word for a change.
Description, as the server wrote it Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
analyze_prospectsRun the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals.No findings
Why it is in this group
- The name "analyze_prospects" says "analyze": a word for reading.
- The description's first verb is "run": a word for a change.
Description, as the server wrote it Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals. Every signal kept must quote its source verbatim. Counts against the monthly analysis quota. Slow: expect up to a few minutes.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
create_custom_signalTeach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long").No findings
Why it is in this group
- The name "create_custom_signal" says "create": a word for a change.
Description, as the server wrote it Teach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long"). Future analyses and sourcing will use it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
draft_emailWrite a personalised email for a prospect, built from their detected signals, in their language.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it Write a personalised email for a prospect, built from their detected signals, in their language. Saves the draft on the prospect and returns it. Does not send.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
draft_linkedin_messageWrite a short LinkedIn connection note for a prospect from their detected signals, in their language.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
Description, as the server wrote it Write a short LinkedIn connection note for a prospect from their detected signals, in their language. Saves the draft and returns it. Does not send.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
find_leads_from_signalsSearch recent LinkedIn posts on the topics of this account's own signal definitions, keep only posts a check can prove are on topic, and return the people who wrote, commented on o…1 finding
Why it is in this group
- The name "find_leads_from_signals" says "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "find_leads_from_signals" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "find_leads_from_signals" says "find": a word for reading.
Description, as the server wrote it Search recent LinkedIn posts on the topics of this account's own signal definitions, keep only posts a check can prove are on topic, and return the people who wrote, commented on or reacted to them, filtered against the ICP (role, industry, country) and ranked. Nothing is saved: pass the returned candidates to import_sourced_leads. Spends a little of the monthly sourcing budget.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
import_sourced_leadsSave candidates returned by find_leads_from_signals.No findings
Why it is in this group
- The name "import_sourced_leads" says "import": a word for a change.
Description, as the server wrote it Save candidates returned by find_leads_from_signals. They arrive already enriched and with the signal attached, including the verbatim quote from the post that surfaced them. Counts against the import quota.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
mark_email_sentRecord that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.No findings
Why it is in this group
- The name "mark_email_sent" says "mark": a word for a change.
Description, as the server wrote it Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 5Claude Code: allow
get_icpThe active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions.No findings
Why it is in this group
- The name "get_icp" says "get": a word for reading.
Description, as the server wrote it The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_pipeline_statsHow the pipeline stands: how many prospects, how many carry signals, enrichment state, how many have an email address, how many were contacted, what was added in the last 7 days, t…No findings
Why it is in this group
- The name "get_pipeline_stats" says "get": a word for reading.
Description, as the server wrote it How the pipeline stands: how many prospects, how many carry signals, enrichment state, how many have an email address, how many were contacted, what was added in the last 7 days, the most common signal types, and the remaining plan quota.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_prospectEverything known about one prospect: role, company, location, language, every detected signal with the verbatim quote from its source and the LinkedIn URL it came from, any existin…No findings
Why it is in this group
- The name "get_prospect" says "get": a word for reading.
Description, as the server wrote it Everything known about one prospect: role, company, location, language, every detected signal with the verbatim quote from its source and the LinkedIn URL it came from, any existing email or LinkedIn draft, and outreach state.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_prospectsSearch the saved prospects in the account.No findings
Why it is in this group
- The name "list_prospects" says "list": a word for reading.
Description, as the server wrote it Search the saved prospects in the account. Filter by company, industry, job title, country, signal type, minimum number of signals, whether an email address is known, enrichment state, or whether they have been contacted. Ordered by signal count, then most recently saved.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_signalsThe buying signals this account looks for: the predefined ones and the custom ones, each with the definition used to detect it and whether it is enabled.No findings
Why it is in this group
- The name "list_signals" says "list": a word for reading.
Description, as the server wrote it The buying signals this account looks for: the predefined ones and the custom ones, each with the definition used to detect it and whether it is enabled. Use the returned type values with list_prospects and find_leads_from_signals.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__linkedin-buying-signals__list_prospects",
"mcp__linkedin-buying-signals__get_prospect",
"mcp__linkedin-buying-signals__get_pipeline_stats",
"mcp__linkedin-buying-signals__list_signals",
"mcp__linkedin-buying-signals__get_icp"
],
"ask": [
"mcp__linkedin-buying-signals__add_leads_from_urls",
"mcp__linkedin-buying-signals__find_leads_from_signals",
"mcp__linkedin-buying-signals__import_sourced_leads",
"mcp__linkedin-buying-signals__analyze_prospects",
"mcp__linkedin-buying-signals__draft_email",
"mcp__linkedin-buying-signals__draft_linkedin_message",
"mcp__linkedin-buying-signals__mark_email_sent",
"mcp__linkedin-buying-signals__create_custom_signal"
],
"deny": [
"mcp__linkedin-buying-signals__send_email",
"mcp__linkedin-buying-signals__send_linkedin_message"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as linkedin-buying-signals. Review it before you use it.