Skip to main content
Glama
298,188 tools. Last updated 2026-07-14 11:30

"linkedin" matching MCP tools:

  • Generate a secure LinkedIn connect (or reconnect) link the user opens in their browser to authenticate. Use when get_linkedin_status shows not connected/blocked, or after an ACCOUNT_NOT_CONNECTED/ACCOUNT_BLOCKED error. Returns a white-labeled https://auth.salesbot.cz link valid ~2 hours; the user just opens it and finishes LinkedIn login — nothing else is needed. profile_id optional (defaults to active/first profile). Set reconnect=true to reconnect an existing blocked/expired account.
    Connector
  • Preferred user-facing LinkedIn account analysis and account health dashboard. Renders the LinkedIn account readiness report with setup recommendations, probe evidence, and technical details. Use this directly when a user asks for LinkedIn account analysis, account health, connector readiness, setup diagnostics, or whether a LinkedIn Ads account is ready for reporting. It can take healthPayload from linkedin_get_account_health or run the same health checks directly. If accountId is omitted, the most recent LinkedIn account from session memory is used when available.
    Connector
  • Identify what a LinkedIn URL points at before fetching it. Give any LinkedIn profile, company, or post URL (utm params, www/m subdomains, trailing slashes are fine); get back {type: person|company|post, id, handle, canonical_url}. For profile URLs, id is the stable person URN; for company URLs, id is the stable company URN; for post URLs, id is the activity URN extracted from the URL. For people, use the returned handle or id with get_profile or get_posts. For companies, use the returned HANDLE with get_company or get_posts; the company URN/id is a search_people filter input, not a fetch identifier. Costs 2 credits. Skip this tool when you already have a slug, URN, or clean URL: get_profile and get_company accept those directly, so resolving first would waste 2 credits. Not for non-LinkedIn URLs; it returns INVALID_INPUT for those.
    Connector
  • User-facing LinkedIn creative comparison visual report renderer. Current app template: ui://linkedin/creative-comparison-v4.html. Use this directly when a user asks for a LinkedIn creative comparison visual report, creative performance report, creative winners/losers, or which creative concepts are performing strongest. It renders the visual MCP app with Overall/campaign views, creative action cards, primary results, diagnoses, and bottleneck diagnosis. It can either take comparisonPayload from linkedin_compare_creative_performance or fetch the comparison directly. For account-wide creative analysis, pass accountId and omit campaignId/campaignIds, or pass advertiserName/query so saved advertiser context or live account-name matching can resolve the LinkedIn account. Name-only account-wide requests are supported; do not claim the renderer requires a numeric accountId until this tool returns an account-selection blocker. lookbackDays accepts numbers and string aliases such as "30d", "30 days", and "past 30 days"; do not claim a numeric lookback is required. If accountId and name/query are omitted, the most recent LinkedIn account from session memory is used when available. For campaign-specific creative analysis, pass campaignId or campaignIds; if accountId is also supplied as parent context, set scope to campaign when possible. accountId plus campaignIds is accepted as a campaign-set compatibility shape.
    Connector
  • Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.
    Connector
  • List the user's connected social media accounts (Instagram, TikTok, LinkedIn) so you can offer to publish content for them. Returns whether the Connectors add-on is active and the connected accounts. Read-only, no credits. Call this before offering to post, or when the user asks to publish.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • LinkedIn data for AI agents: search, profiles, companies, posts. No key needed to start.

  • linkedin-humblebrag MCP — wraps StupidAPIs (requires X-API-Key)

  • Publish a post immediately to the user's connected social accounts (Instagram, TikTok, LinkedIn, X, Threads). ALWAYS confirm with the user first (target platforms + caption). Instagram and TikTok require at least one image or video in media_urls; LinkedIn, X, and Threads allow text only. Caption limits: X 280 chars, Threads 500 chars. X has a monthly allowance of 50 posts included in the add-on. Pass generated asset URLs (Supabase-hosted) as media_urls. LinkedIn also supports DOCUMENT posts (rendered as a swipeable carousel): pass exactly ONE .pdf/.ppt/.pptx/.doc/.docx URL in media_urls, targeting linkedin only. Document rules: one document per post, never mixed with images or videos, max 100 MB and 300 pages, password-protected PDFs are not supported, and the URL must serve the file bytes directly (Supabase-hosted works; Drive/Dropbox/OneDrive share links do not). Set document_title for document posts, and put any external link in first_comment instead of the caption (LinkedIn suppresses captions with links). If the user isn't subscribed or hasn't linked the platform, the result will instruct you to show a connect card, do not retry in that case.
    Connector
  • Read-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server. Call this first — this endpoint is a discovery stub with no LinkedIn powers.
    Connector
  • Research a person before outreach: returns a synthesized profile (current role, company, location, career history, education, LinkedIn/social URLs) plus a candidates array for disambiguating namesakes. Use to personalize a first touch or brief before a meeting. Does NOT return contact channels (email/phone/telegram) — use contacts.discover to add a reachable channel, or the LinkedIn URL from the result for a connection request.
    Connector
  • Check your balance, plan, limits, and the last 10 charges (receipt ids included). Costs 0 credits and is exempt from the per-minute rate limit, so call it whenever you need to budget. The response includes upgrade_url (give it to your human when credits or plan limits block you; purchases credit this account directly with no login) and manage_url (give it to your human to change or cancel a paid plan in the Stripe billing portal). Trial accounts also get a claim_url that attaches an email so the account can be recovered if the key is lost. Requires an API key: keyless calls have no account, and each keyless response already reports its cost in the usage block. Not for fetching LinkedIn data.
    Connector
  • Identify what a LinkedIn URL points at before fetching it. Give any LinkedIn profile, company, or post URL (utm params, www/m subdomains, trailing slashes are fine); get back {type: person|company|post, id, handle, canonical_url}. For profile URLs, id is the stable person URN; for company URLs, id is the stable company URN; for post URLs, id is the activity URN extracted from the URL. For people, use the returned handle or id with linkedin_get_profile or linkedin_get_posts. For companies, use the returned HANDLE with linkedin_get_company or linkedin_get_posts; the company URN/id is a linkedin_search_people filter input, not a fetch identifier. Costs 2 credits. Skip this tool when you already have a slug, URN, or clean URL: linkedin_get_profile and linkedin_get_company accept those directly, so resolving first would waste 2 credits. Not for non-LinkedIn URLs; it returns INVALID_INPUT for those.
    Connector
  • Find people on LinkedIn by keywords and filters. The right tool when you have a name, role, or 'who is the X at Y' question without a profile URL. Pass keywords (free text: name, title, or both) and any of first_name, last_name, title, school, current_company, past_company. If keywords is omitted it is derived from the name or title filters; school or company filters alone are rejected with INVALID_INPUT, so include keywords with those. Company filters accept a company name, slug, numeric id, or URN; names are resolved for you. Costs 10 credits including the first 10 results; each further 10 results add 1 credit (limit max 30; keyless and trial callers max 10). A cursor page is a NEW call priced the same way by its own limit, so one limit=30 call is much cheaper than three limit=10 pages; prefer a larger limit over paginating. Do NOT combine a company NAME filter with limit=30: name resolution spends one of the call's three internal fetches, so that combination is rejected. With a company name keep limit<=20; for limit=30 pass the company's numeric id or URN (linkedin_get_company returns both). Returns name, position, location, urn, public_identifier per result, a cursor for the next page, and total_matches. Results with is_anonymous=true are private profiles; do not pass them to linkedin_get_profile. For one known person with a URL/slug, call linkedin_get_profile directly instead.
    Connector
  • Fetch one person's LinkedIn profile. identifier accepts a profile URL, the slug after /in/ (e.g. 'williamhgates'), or a urn:li:fsd_profile URN; URLs are cleaned automatically. Always returns the overview (name, headline, location, current position, follower counts) plus up to 2 requested sections from about|experience|education|skills at no extra cost; each section beyond 2 adds 2 credits (max 4 sections). Costs 4 credits base. If you only have a name, use search_people first; this tool does not search. Results from search_people with is_anonymous=true cannot be fetched here; treat them as 'someone matching this exists' and stop. Companies belong to get_company.
    Connector
  • Fetch the recent LinkedIn posts of one person or one company. identifier accepts a profile or company URL, a slug, a person URN, or a company website domain like 'microsoft.com'; the entity type is detected automatically. A domain resolves to its verified company first, exactly like get_company: it QUOTES base+4 credits (set max_credits accordingly) and the surcharge is refunded at settlement for already-known domains, so they settle at the base price. Company URNs and numeric company ids are search-filter inputs, not fetch identifiers: use the company slug, URL, or domain here. Returns one page of posts (text, created_at, author, likes, comments_count, shares, is_repost, url) with a cursor for older posts. Costs 4 credits per page. Use this for 'what has X been posting', voice-of-company research, or activity checks before outreach. Not for reading one specific post you already have a URL for, and not for keyword search across LinkedIn; neither is supported in v1.
    Connector
  • Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import
    Connector
  • Google X-Ray search for public LinkedIn profiles via Google operators (site:linkedin.com/in). Useful when you don't want to consume LinkedIn search limits. Found profiles are saved into your contacts (in a 'Google X-Ray' list, deduplicated by profile URL) and the tool returns their contact_id values. To move them into the CRM, add them to a campaign with add_contacts_to_campaign (auto-creates CRM leads) or use a CRM tool like set_deal_stage. Paginates Google results and auto-filters duplicates.
    Connector
  • 🔗 Link a new channel identity (email, phone, LinkedIn, etc.) to an existing contact. When to use: - User learns a contact's email or phone and wants to save it - User wants to link a LinkedIn/Instagram profile to an existing contact - Adding a second channel for an existing person Requires contact_id (entity_id) from contacts.find.
    Connector
  • Send a message to a thread, channel, or contact. Supports Telegram, Email, LinkedIn, and other connected channels. For LinkedIn posts (comment_thread kind), this posts a comment on the post. Can automatically resolve recipients and channels when not specified. Can send files/images/documents as attachments — pass `attachments=[file_id, ...]` with integer file IDs obtained from collections.list_files, search.files, or files.search. `text` is optional when attachments are provided.
    Connector
  • P116 — paste-what-you-see metric fallback for channels without public-API measurement (X, LinkedIn, Email, landing pages, Product Hunt). USE WHEN a published action's channel doesn't have a public-JSON metrics endpoint (anything except hacker_news / reddit) AND the founder is ready to paste the visible numbers. Reads metadata.proof.artifactUrl to confirm the post is recorded, writes the provided metrics into metadata.proof.metrics + measuredAt, auto-classifies the outcome (channel-specific thresholds: X needs likes/replies, LinkedIn needs reactions/comments, Email needs opens/clicks/replies, etc.), and creates next-move actions just like the auto-measurement path. Returns the metric schema for the channel so callers can render the right form fields.
    Connector
  • Schedule a post for a FUTURE time on the user's connected social accounts (Instagram, TikTok, LinkedIn, X, Threads). ALWAYS confirm with the user first (platforms, caption, and the exact time). Instagram and TikTok require at least one image or video in media_urls; LinkedIn, X, and Threads allow text only. Caption limits: X 280 chars, Threads 500 chars. LinkedIn also supports DOCUMENT posts: exactly ONE .pdf/.ppt/.pptx/.doc/.docx direct file URL in media_urls, targeting linkedin only, never mixed with images or videos (max 100 MB / 300 pages; password-protected PDFs unsupported). Set document_title for document posts and put external links in first_comment instead of the caption. Provide scheduled_for as an ISO 8601 timestamp; include the user's timezone if you know it. If the user isn't subscribed or hasn't linked the platform, the result will instruct you to show a connect card.
    Connector