Skip to main content
Glama
271,551 tools. Last updated 2026-07-08 03:27

"A search for advanced LinkedIn features or tools for exploring profiles and connections" matching MCP tools:

  • 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
  • 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
  • Search for contacts by title, company, or query. Searches saved Xmagnet contacts first (free, instant), then a profile-first prospecting page of up to 50 profiles (free, emails HIDDEN). Examples: 'CTOs in Denver', 'John Smith at Google', 'VPs of Sales at SaaS startups'. Emails are not included — to reveal one, call find_email for that person (4 credits per verified find). Use load_more_contacts for the next page.
    Connector
  • Check whether a company holds a UK or Netherlands work-visa sponsorship licence. The register lists official registered legal entity names, not brand, product, or trading names. If the user provides a brand name, product name, or website, first determine the company's registered legal name (via web search, the company's own website, or the relevant companies register) and pass that. Tolerates minor typos but not brand-vs-legal-name mismatches. Returns licence routes, ratings, locations and register dates. If results are ambiguous or none are found, refine the legal name and try again. For exploring or filtering many companies, use search_sponsors instead.
    Connector
  • Search for humans available for hire. Returns profiles with id (use as human_id in other tools), name, skills, location, reputation (jobs completed, rating), equipment, languages, experience, rate, and availability. All filters are optional — combine any or use none to browse. Key filters: skill (e.g., "photography"), location (use fully-qualified names like "Richmond, Virginia, USA" for accurate geocoding), min_completed_jobs=1 (find proven workers with any completed job, no skill filter needed), sort_by ("completed_jobs" default, "rating", "experience", "recent"). Default search radius is 30km. Response includes total count and resolvedLocation. Contact info requires get_human_profile (registered agent needed). Typical workflow: search_humans → get_human_profile → create_job_offer.
    Connector
  • Batch-fetch up to 100 profiles by (platform, username) pairs. Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to `get_profile`. Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use `get_profile`. For partial or fuzzy handle/name input, use `search_creators` or `autocomplete_creators`. Use `semantic_search_creators` only for topical/niche/audience discovery where false-positive semantic matches are acceptable. Examples: - User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch. - User: "Give me follower counts for these 30 accounts" -> use this tool. - User: "Find wellness creators in Austin" -> use `semantic_search_creators`, not this tool. The response splits results into `data` (profiles found) and `not_found` (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

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

  • Search and browse AI tools available in Vest's cashback catalog. Returns names, slugs, categories, and live cashback rates. Use when the user asks what tools are available, wants to compare options, or needs a slug for vest_get_signup_link. Real triggers: 'what AI writing tools does Vest have?', 'show me coding tools with high cashback', 'find tools under $50/mo'. Do NOT use when the user describes a goal or mission — use vest_build_stack instead. Do NOT use to get a signup link — use vest_get_signup_link.
    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
  • The acting user's personalized feed — posts from their communities, accepted connections, and follows, ranked by a relevance score (recency × engagement × graph affinity). Blocked profiles filtered out. Use for 'show me my feed' / 'what should I read'. Do NOT use to answer 'what did my communities post today?' — that's a chronological window question; use `get_recent_posts` with a `since` timestamp instead, since this tool will surface yesterday's high-engagement posts over today's quiet ones.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Index a video for search, QA, or full analysis. Processes the video through a pipeline of AI features. Typically takes 3-7 minutes; longer for long videos or the 'full' pipeline. Times out after 10 minutes by default. Pipelines: - search_only: transcription + captions + embeddings (enables search_videos) - qa_only: transcription + captions (enables ask_video) - full: transcription + captions + embeddings (enables all tools) Scene detection is enabled by default and produces scene boundaries for get_scenes. Pass scene_detection=False to skip it. Prerequisites: if using video_id, the video must be in 'uploaded' status. Use get_video to check status before calling this tool.
    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
  • Fetch public Steam profiles for up to 100 comma-separated SteamID64s in one request; returns persona name, avatar, country, and status for each.
    Connector
  • Global Waymarked Trail & Mountain Route Explorer. Queries real-time OpenStreetMap relation networks for designated hiking, biking, and mountain trails anywhere in the world. USE FOR: - "How long does it take to hike up Črna Prst from Podbrdo?" - "Are there any marked mountain paths near this coordinate?" - "Find biking or mountain biking (MTB) trails around this area." - Discovering waymark symbols, route difficulty metrics, and trail networks. CRITICAL INSTRUCTIONS FOR AGENT: - Use this tool instead of standard street routers (`geo-route`) if the destination is a mountain peak, ridge, national park trail, or alpine hut. - Set a small buffer (e.g., 0.005 for 500m, up to 0.02 for ~2km) around coordinates to avoid massive data payloads. - Accept the features returned by this tool as complete. DO NOT iteratively search or run multiple tag queries sequentially. Read the returned trail distances, calculate speed profiles, and answer immediately. NOT FOR: Street-grid driving directions, finding urban shops/cafes, raw city geocoding.
    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
  • Advanced: Submit a pre-signed transaction to Solana. Only needed if you used create_stake_transaction/create_unstake_transaction/withdraw_stake and signed locally. Most agents should use the one-shot stake/unstake/withdraw tools instead.
    Connector
  • Search for username across 15+ social/dev platforms (GitHub, Reddit, X/Twitter, LinkedIn, Instagram, TikTok, Discord, YouTube, Keybase, HackerOne, etc.). Use for OSINT investigations and identity verification. Free: 30/hr, Pro: 500/hr. Returns {username, total_found, platforms: [{name, exists, url, status_code}]}.
    Connector
  • Curated catalog of all available paid Askew endpoints with pricing, sample calls, and buyer intent context. Best starting point for agents exploring what Askew sells. No payment required.
    Connector
  • Get full details for a specific company by its ID. Returns the complete company profile including features, use cases, pricing, and contact info. Args: company_id: The UUID of the company (obtained from search results) Returns: Complete company profile dictionary, or an error if not found.
    Connector