Skip to main content
Glama
816,409 tools. Updated 2026-11-21 14:09

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

  • List LinkedIn 1st-degree connections for an account (Voyager dash connections), paged with start/count — same payload as GET /api/linkedin/{account_id}/connections. Use to walk the account's own 1st-degree network; for pending invitations use list_sent_invitations or list_received_invitations; for search use scrape_search.
    ConnectorAPI key
  • List LinkedIn 1st-degree connections for an account (Voyager dash connections), paged with start/count — same payload as GET /api/linkedin/{account_id}/connections. Use to walk the account's own 1st-degree network; for pending invitations use list_sent_invitations or list_received_invitations; for search use scrape_search.
    ConnectorOAuth
  • Generate a Mermaid.js flowchart for human visual inspection only. NOT for orphan detection or programmatic analysis — use audit(mode=orphans) to find isolated memories. Output may be truncated for large domains; never infer graph properties (e.g. orphans) from a truncated result. Pass memory_id (memory ID) to see a single memory and all its direct connections. Pass domain to see the full domain graph (most-connected memories first, capped at limit, default 40 max 100). Returns JSON with mermaid, node_count, edge_count, nodes_shown, nodes_total, edges_shown, edges_total, truncated, memories([{id,label}]) and connections([{from,to,relationship}]). If client supports HTML widgets, prefer passing memories and connections to an interactive renderer rather than outputting raw mermaid. If not, output mermaid inside a ```mermaid code block. If truncated is true, note only most-connected memories are shown and nodes_total/edges_total reveal what was dropped.
    ConnectorAPI key
  • Query synaptic connectivity between Drosophila neuron classes across ALL connectome datasets simultaneously for comparative connectomics. This is NOT pre-cached — it runs live queries, so expect slow responses (up to several minutes). Set both upstream_type AND downstream_type to filter connections between two specific neuron classes (e.g., "What Tm1→T3 connections exist across all datasets?"). At least one of upstream_type or downstream_type is required. CONSTRAINTS: Only accepts neuron class terms (OWL IDs like FBbt_00003789 or labels like "transmedullary neuron Tm1") — anatomical regions or neuropils (e.g., "lobula", "medulla") are NOT accepted. NOT suitable for individual neuron-to-neuron connections — for pre-computed connections of a single individual neuron, use run_query with NeuronNeuronConnectivityQuery instead. NOT for muscle/sense organ connections. RECOMMENDED DEFAULTS: weight=5, exclude_dbs=["hb","fafb"] unless user specifies otherwise. For both-ends queries, start with weight≥50 to avoid timeouts. RESULT SIZE: a broad query is enormous (a single class at weight=5 can be over 50,000 connections), so results are ranked strongest-first and paged — you get limit rows (default 50) plus a summary computed over ALL of them: totals, per-dataset counts, distinct neuron counts, and the top class pairs. Answer from the summary and quote a handful of rows; only page with offset if the user asks for specific further rows. WORKFLOW: Confirm parameters with user before querying. Use search_terms with filter_types ["neuron","class"] to validate/canonicalize neuron type labels. If zero results, try relaxation: lower weight to 1, then remove exclude_dbs filter, then try group_by_class=true — report what worked and let user decide. group_by_class=true is usually the better first call on a broad query: it rolls the connections up over the subclass hierarchy — a row per (upstream level, downstream level) with data, up to the queried term(s) — instead of returning every neuron pair. Because a connection counts toward every ancestor pair in scope, per-row pairwise_connections and total_weight do NOT sum to the raw connection counts, and a row appears for the queried class itself as well as each subclass with data.
    ConnectorNo auth
  • Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.
    ConnectorNo auth
  • Present a selection of tours or activities to the traveler as a visual list of cards (photo, rating, price, booking button) rendered inline in the conversation. Showing cards is the default way to present tours to the traveler: whenever your reply features specific tours (recommendations, a shortlist, availability results), call this tool alongside your text instead of waiting to be asked. Don't re-render a selection you already showed unless it changed. Call it AFTER finding tours with the search tools — it is a presentation tool, not a search tool. If you already checked availability with get_product_availability, you can pass each item's sessions (date and start time) and the cards will highlight them with booking links preselecting the date. For clients without UI support the same data is returned as structured text.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Decision Layer for AI Agents — 58+ tools, Advisor, MCP. Free key: POST /v1/register {}.

  • Post deals, host events, import contacts and keep notes and memory across every assistant.

  • Generate synthetic / fake user profiles via the MwVideos random_users API (POST /mwvideos/api/random_users). Returns name, gender, location, email, login, dob, phone, picture, and nat. Use when the user asks for random users, fake people, sample contacts, demo personas, UI fixtures, or test profiles. Pass `results` for how many profiles (default 1, minimum 1) and `isPro` as 0 or 1 when relevant (default 0). Authenticated user_id is injected server-side — do not invent profiles; always call this tool. These are FAKE people for demos and testing, not real PII.
    ConnectorOAuth
  • Use when the user asks about one Steam account itself - nickname, avatar, profile visibility, creation date, online status, current game - and nothing else. Returns the raw GetPlayerSummaries object plus SteamID conversions; cheapest profile tool, data no older than 48 hours, unknown profiles are fetched live from Steam. Private profiles return the public subset of fields (not an error); unresolvable ids return an error result. Do not use for bans, FACEIT or friends (steam_summary or the narrow tools).
    ConnectorNo auth
  • Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.
    ConnectorNo auth
  • Discover available product features, API/MCP URLs, versions, content limits, and interpretation boundaries before choosing a content tool. Returns product.capabilities.v1 metadata, without fetching stories or checking upstream freshness. Public and read-only; no credentials or arguments. Use latest_stories for recent records or get_health for endpoint compatibility. The mobile app distribution channel remains separately suspended.
    ConnectorNo auth
  • The user's LinkedIn post analytics from LinkedIn's own API (their connected account) — impressions, unique members reached, reactions, comments, and reshares. Use for questions like 'how many impressions did I get last month?' or 'how are my posts performing?'. Omit dates for lifetime totals; pass start_date/end_date for a window; set daily=true (with one specific metric) for a per-day series to describe trends. Numbers are live from LinkedIn, unlike get_my_linkedin_posts whose per-post counts come from a periodic sync.
    ConnectorNo auth
  • Synchronize one provider-safe page (at most 500) of the API-key owner's 1st-degree LinkedIn relations into the local workspace cache. This is a provider read, not a LinkedIn people search, and does not consume the search quota. The server persists continuation state and atomically enforces a 15–20 minute delay, four-page hourly cap, and twelve-page daily cap across UI and MCP. Respect RELATIONS_SYNC_PROTECTED retry_after_seconds before continuing.
    ConnectorAPI key
  • Discover the LinkedIn company pages this connected account administers. Reuse the selected data[].id (NOT mailbox_id) with the SAME account_id as post_as for linkedin_create_post, comment_as for linkedin_comment_on_post/linkedin_reply_to_comment, or react_as for linkedin_react_to_post/social_react_to_comment. Requires the company product selected in Hosted Auth; if access is refused, reconnect the SAME account with account_connect and select Company Pages. A company search result does not prove admin rights; never fall back to acting as the person.
    ConnectorOAuth
  • Use this when you need to review what a Study found: aggregate evidence, findings, citation references, freshness and next action. Standard connections also receive paginated individual rating feedback by default. Managed connections return aggregate findings by default; includeFeedback=true requires original-source permission and adds the feedback feed with participant identity. feedbackLimit and feedbackOffset page that feed. Use studies.get_responses for individual research answers; that is a separate original-source read.
    ConnectorOAuth
  • PERMANENTLY delete saved contacts (LinkedIn profiles) including their campaign memberships, scheduled actions and campaign history. Contacts with pending or in-progress campaign steps are refused unless force: true (prefer exclude_contacts_from_campaign when the goal is just to stop outreach). Linked CRM leads are kept (unlinked) unless delete_crm_leads: true. Cannot be undone: only on the user's explicit request, show them the contacts first and pass confirm: true after they agree.
    Connector
    Destructive
    API key
  • The top organic results and SERP features Google shows for one query. Use when: "what ranks for X", "who is on page one for X", "is there a featured snippet or AI overview for X". Not for: where one site ranks for a keyword, use seo_get_position (it scans the top 100 for you). Keyword ideas, use seo_search_keywords. The businesses Google Maps ranks for a local search, use maps_search_places. Returns: Record. features[] (featured_snippet, people_also_ask, video, ai_overview and others), results[] (rank, organic_rank, type, url, domain, title, snippet, published_at, rating), related_searches[], ai_overview (text, references[]) or null, results_count, check_url. depth counts organic rows: the default returns 10 organic results whenever Google has them, with the features ranked among them on top. Each People Also Ask question and each forum thread is its own row at its block's rank; for a question, title is the question and snippet the answer, url null when Google's answer is an AI overview. domain is null on a row whose url is still a google.com/goto redirect. location localises the local pack, not the organic rows of a bare service search: put the town in the keyword ("dentist columbus ohio") for local organic results. Paid ads seldom come back, so the page says nothing about who bids on the query; a named rival's search ads are in ads_get_advertiser_ads with platform google. Cost: 1 credit per 10 results, +1 with ai_overview. Default top 10 = 1 credit. Cached 24 hours. Example: {"keyword": "hubspot alternative", "depth": 10, "ai_overview": true}
    ConnectorAPI key
  • The comments LinkedIn shows on one post, each with the commenter's profile URL. Use when: pulling the people who engaged with a post: a competitor's launch, a thought leader in your category, your own post. Each author_url goes straight into linkedin_get_profile or leads_get_person. Not for: every comment on a busy post (LinkedIn shows up to 10 to a logged-out reader, so a post with 200 comments returns 10). Reactions, which LinkedIn does not show at all. Many posts at once, use linkedin_search_posts, whose rows carry the same commenters in top_comments. Returns: List. rows[]: one comment each: author (the profile's slug, the part after /in/ or /company/), author_url (on www.linkedin.com), text (cut at 2000 characters). LinkedIn gives no time, likes or replies for a comment, so those are null. meta.cursor is always null: there is no next page. Cost: 1 credit. Cached 6 hours. Example: {"url": "https://www.linkedin.com/posts/aagupta_what-you-need-to-know-ai-agents-activity-7354600338621906944-RvXR"}
    ConnectorAPI key
  • Pulls fresh comment threads and DMs from the connected platforms (Instagram, Facebook, YouTube, Threads, LinkedIn) into ShortSync's inbox cache. Same operation as clicking the refresh button in the inbox UI. Returns a per-connection DmSyncResult with counts of new conversations and messages plus any errors. Call this before list_inbox_conversations when the user asks for the latest activity — otherwise the tool serves cached data from the last sync. Hits the platform APIs so it counts against rate limits. Threads is beta-gated behind DM_INBOX_THREADS and LinkedIn behind DM_INBOX_LINKEDIN — accounts without the flag see those connections silently skipped rather than an error. LinkedIn coverage is uneven per account: only organization-context connections with r_organization_social can read post comments; personal-profile posts require partner-tier API access we don't have and return no conversations.
    ConnectorOAuth
  • `get_planning_signals` — what is HAPPENING around Scripe profiles, for planning from evidence, in ONE bounded call (up to 10 profiles; omit `profileIds` for every profile you can reach). Returns: (1) `niche` — what works on LinkedIn right now among people like each profile: recent posts by OTHER people that beat their own author's usual engagement (`outlierMultiple`), with opening, format, lane, author and link, each listed once with the `profileIds` it is relevant to; (2) `sourceItems` — what the profiles' followed sources published since `sourcesSince` (default 7 days ago), with each profile's match score and the For You idea it already became; (3) per profile `performance` — THE source of performance numbers: its own posts of the last 90 days by post format (with lane), lane, media format and content topic, each with a `lift` against that profile's own median, headed by `summary` — what performed for that profile, in words: plan more of it and say what you learned; quote a lift from the profile it sits under; (4) per profile idea stock — `forYou` (the strongest unsaved For You ideas per lane, WHY Scripe picked each and its source) and `board` (unplaced board ideas); raise `ideasPerLane` for a long plan instead of paging `list_for_you_ideas` per profile; (5) `knowledge` — knowledge-base documents added in the last `knowledgeDays` (default 30: meetings, interviews, files, synced docs), each with its opening (a recording's chapters) and the profiles that can use it; (6) `knowledgeSummaries` — per profile the most relevant document Scripe already summarised (its own first, then the one matching its content topics; last 180 days): every chapter with its summary, or a meeting's own summary — cite it by name in an idea's notes; read one whole with `read_knowledge_document`. Nothing is ranked or chosen for you: weigh it yourself, then write ideas in `preview_plan`. `include` narrows the sections; `detail: "full"` widens every list. Every answer stays under a host's inline limit: `trimmed: true` says list tails were cut — ask again for fewer `profileIds` or a narrower `include`.
    ConnectorOAuth
  • Searches Google Jobs, which collects postings from many job sites, and returns up to 20 jobs from the first page (title, company, location, via, details, apply_url). Put role and place in the query, e.g. "data engineer jobs in Austin". It does not return full job descriptions or people profiles; for LinkedIn listings with LinkedIn filters use search_linkedin_jobs. A search with no matches is charged; errors are not. Required: query.
    ConnectorNo auth
  • When a social set's own published posts have done best: the 6 strongest weekday and hour slots on the set's clock, best first, each with how many posts it holds and their average engagement (likes + comments + shares or reposts, whichever is larger, + saves) per post. A slot whose posts earned nothing is left out, so a set with no engagement yet gets no slots. Says the set's time zone and how many posts were read. LinkedIn posts aren't counted, since LinkedIn doesn't allow its numbers in AI apps; a set that posts only to LinkedIn gets starter times from a public study and its own posting slots. To post at the best time on any platform, LinkedIn included, schedule_post with when "best_time" lets Buzzmark pick. For how single posts did, use get_post_stats, and for what the posts have in common, get_insights.
    ConnectorAPI key