Skip to main content
Glama
134,441 tools. Last updated 2026-05-23 15:47

"Finding people on LinkedIn using their names" matching MCP tools:

  • List all available Alpha Vantage API tools with their names and descriptions. IMPORTANT: This returns only tool names and descriptions, NOT parameter schemas. You MUST call TOOL_GET(tool_name) to retrieve the full inputSchema (required parameters, types, descriptions) before calling TOOL_CALL. Calling TOOL_CALL without first calling TOOL_GET will fail because you won't know the required parameters. Workflow: TOOL_LIST -> TOOL_GET(tool_name) -> TOOL_CALL(tool_name, arguments)
    Connector
  • Permissions inquiries people send about using the artist's work — the contact loop on the Declared section (Access model mechanism 7). Artist side only; public submission is the web form's job. action "list": the inbox, all states (pending, in_progress, granted, granted_with_conditions, declined, expired, withdrawn) — read-only; surface pending first. TRIGGER: "any rights requests," "who wants to use my work," "open my rights inbox." action "get": one request by id (requester, the use asked about, the declared right referenced, response so far) — read-only. action "respond": a signed, dated grant / grant_with_conditions / decline (the requester sees it on their status page; the artist email is never shared). `decision`=grant_with_conditions requires ≥1 structured term in response_payload; response_message is always required. Confirm the decision with the user first — the requester is notified immediately. Find request_id via action "list" — never ask the user.
    Connector
  • Transfer multiple ENS names in a single transaction via Multicall3 — bulk send. Much cheaper and faster than transferring names one at a time. Supports up to 20 names per batch. Automatically detects whether each name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transfer call for each. All names can go to the same recipient or to different recipients — specify a toAddress per name. Requirements: - The fromAddress must currently own ALL names in the batch - All addresses must be valid Ethereum addresses - Names must be registered (not expired) WARNING: This transfers FULL ownership of every name. Recipients gain complete control. Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on each name. After transfer, consider using bulk_set_records to update ETH address records on the transferred names.
    Connector
  • List all supported surf pools worldwide with their IDs, names, and locations. Always call this first to get valid pool_id values for the other tools.
    Connector
  • List all infrastructure role categories with their mapped nodes. Use this to browse all available equivalence mappings, or to disambiguate node names when find_equivalent reports ambiguity. Returns a list of category dicts, each with: category (str): Category identifier (e.g. 'virtual_machine'). description (str): Human-readable description. providers (list[str]): Providers covered by this category. nodes (dict): Mapping of provider → list of node names in that category.
    Connector
  • Creates a visual edit session so the user can upload and manage images on their published page using a browser-based editor. Returns an edit URL to share with the user. When creating pages with images, use data-wpe-slot placeholder images instead of base64 — then create an edit session so the user can upload real images.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Returns busy windows for YOU plus a set of named attendees from your Lyra contacts, within a time window. For each attendee you provide, the tool looks up whether their Lyra profile has a connected Google calendar; if so, their busy blocks contribute to the aggregated suggested_free_intervals. If not (or if they're not a linked Lyra profile), they're marked requires_manual_confirm: true so you know to ask them directly. Cap of 8 attendees per call. Privacy: per-attendee busy time ranges are returned, never event titles or summaries. Use this when you need to find a time that works for several people at once. Requires an active Google calendar connection on your own Lyra account and API key authentication.
    Connector
  • Get a list of all banks available on RozbijBank platform. Returns bank titles (use these exact names as bankName filter in SearchPersonalAccounts, SearchSavingsAccounts, SearchDeposits, SearchBusinessAccounts, and SearchPromotions). The bankName filter uses substring matching, so partial names work too.
    Connector
  • STEP 2 of contact upload. Inserts contacts into Xmagnet using the field_mappings confirmed from preview_upload_mapping. Each contact must include the original column names as keys. Requires email per row. Max 500 per call. NEVER call before preview_upload_mapping.
    Connector
  • Composite snapshot of a specific user's activity on a project. Returns an identity block (visitorId, userEmail, userName, firstSeen, lastSeen), total pageviews, total custom events, session count, top pages this user visited, their most-fired event names, and their 20 most recent events with props. Use this for 'how is dancleary54@gmail.com using my app?' style questions — one call, full picture. For ad-hoc drill-down (just a count, just recent events) pass `user` to the individual tools instead. Default window is the last 7 days.
    Connector
  • Atomically move N rows from their current sheet(s) to a target sheet inside the same workspace. Use for programmatic data migration: dropping a batch of agent-produced drafts onto the right sheet, reorganizing content across LinkedIn / Twitter / Substack tabs, etc. All-or-nothing: if any rowId doesn't belong to this workspace, the entire batch fails before any write fires. Idempotent: rows already on the target sheet are skipped (returns `skipped` count). Rows land at the destination sheet's tail in the order rowIds was supplied. Emits one `row.moved_surface` event per row that actually moved. Up to 500 rows per call.
    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
  • List all custom scoring profiles on this account. Returns profile names and their custom weight overrides. Profiles are named weight sets that change how Unphurl scores URLs. Different use cases need different scoring. A cold email agent cares about dead domains. A security bot cares about phishing. Profiles let one account serve multiple use cases. Profiles only override specific weights. Any signal not specified in a profile uses the default weight. Use show_defaults to see all 25 signals and their default weights.
    Connector
  • See what's trending and hot in cryptocurrency right now. Returns the top trending coins on CoinGecko based on search activity and interest. Use this for 'what's trending in crypto?', 'hot cryptocurrencies', 'trending coins', 'what crypto is popular right now?', 'crypto buzz', 'what tokens are people looking at?', or any question about current crypto market interest and momentum.
    Connector
  • Get all sweepstakes associated with your account. Returns a list of all sweepstakes with their details. Use tokens internally for tool chaining but present only human-readable information (names, dates, statuses) to the user. # fetch_sweepstakes Get all sweepstakes associated with your account. Returns a list of all sweepstakes with their details. Use tokens internally for tool chaining but present only human-readable information (names, dates, statuses) to the user.
    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
  • Show the user's default paper size and orientation preferences (set on their account page). Useful when the user hasn't specified pageSize/orientation explicitly — call this to honor their defaults instead of using A4/Portrait blindly.
    Connector
  • Show the user's default paper size and orientation preferences (set on their account page). Useful when the user hasn't specified pageSize/orientation explicitly — call this to honor their defaults instead of using A4/Portrait blindly.
    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, workspace.search, or files.search. `text` is optional when attachments are provided.
    Connector
  • Start asynchronous AI research for a contact using LinkedIn and other sources, then poll the research ID for results.
    Connector