Skip to main content
Glama
683,013 tools. Updated 2026-10-21 03:27

"Tools or methods to automate browser interactions with clicks" matching MCP tools:

  • Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. RECORD THE BROWSER USING A SITE — the showcase capture. A headless browser opens the URL with a VISIBLE cursor drawn on screen and works through `steps` you write: it glides the pointer to a button, clicks it, waits for the page to react, types into fields at human speed, scrolls between sections. THE tool for 'record yourself using my product', a launch/demo video, or 'show how it works', where record_website only pans down a static page. Steps are objects: {do:'click', text:'Start free trial'} (text = the VISIBLE label; or selector: a CSS selector), {do:'type', selector:'input[type=email]', text:'you@example.com'}, {do:'scroll', to:'Pricing'} or {do:'scroll', by:800}, {do:'hover', text:'Plans'}, {do:'press', key:'Enter'}, {do:'wait', seconds:1.5}, {do:'goto', url:'…'}. Add `seconds` to any step to hold longer after it. It returns an EVENT TRACK — every click, scroll and keystroke timestamped with its position in the frame — then place it with showcase_demo, which uses that track. It records the PUBLIC site as a visitor sees it and will not type into password or payment fields. Write 4-10 steps that tell one story; a demo that clicks everything shows nothing.
    ConnectorOAuth
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    ConnectorNo auth
  • Poll AgentPay browser connect until the owner clicks Разрешить. Pass sessionId from begin_agent_link. No API key required. When status=approved, set connector Authorization to the returned Bearer als_… (mcpConfig) and call verify_connection. Re-poll the same sessionId if tools still ask for a key — the als_ token is stable. Never invent keys. Never ask the owner to paste ap_ from Агенты.
    ConnectorNo auth
  • Queries Google Search Console live for the website, or Bing Webmaster Tools with search_engine bing: clicks, impressions, CTR and average position over any period, grouped by query, page, country, device, date or search appearance, with filters (contains, equals, regex). Unlike get_keyword_rankings (tracked keywords synced daily), it reads everything the engine reports; Google works before the website has a plan. Examples: one page's queries (filter page equals its URL); positions 5 to 15 by impressions; brand vs non-brand (query regex filters). Rows are ordered by clicks unless sort is set; metric filters and sort apply to the top 25000 Google rows by clicks. At most 500 rows per call, paged with start_row. Google covers 16 months and lags 2 to 3 days; Bing groups by query, page or date, weekly for queries and pages. 200 calls per hour per website. If it is not connected, the error says where to connect it. Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables structured extraction of methods and reproducibility heuristics from academic papers, allowing AI agents to obtain metadata, full text, structured methods, code repository discovery, and a no-clone reproducibility verdict from a paper URL.
    8
    MIT

Matching MCP Connectors

  • Research methods for AI assistants: study design guidance, R and Python code, and citations

  • Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

  • Use this whenever the question pairs one of YOUR metrics — clicks, impressions, CTR or average position — with market share ("clicks and market share", "impressions vs our share", "are we growing faster than our share", traffic vs share side-by-side). Pass vs:"clicks"|"impressions"|"ctr"|"position" (default clicks) to pick the right axis. Pass country and/or device to keep BOTH legs on the same geography and device (e.g. "clicks and market share on mobile in Canada") — do not decompose that into market_share_query + search_performance. Pass page or category for a FILTERED SUMMARY such as "market share and clicks for pages containing /p/"; that path preserves QWA's summary-level market-share denominator and joins a separately filtered GSC aggregate, so adding traffic cannot change the share definition. Country/device cannot be combined with a page/category summary in the same call. For share vs competitors WITHOUT a traffic metric, use market_share_overview instead. For a per-slice top-N breakdown (e.g. top intents or pages by clicks/share), use market_share_breakdown. Defaults to the primary "default" (Overall Market) segment when omitted — name another tracked segment to scope to it. UNIT CONTRACT: market-share values are already percentage units on a 0–100 scale (0.03 means 0.03%, not 3%); share delta is selected-minus-comparison percentage points; leader gap is leader-minus-client percentage points for the same period; only deltaPct is a relative-change ratio.
    ConnectorOAuth
  • Parses a camt.053.001 bank-to-customer statement XML document with the same schema-subset structural and facet checks as the tools/565 browser reconciliation workbench (IBAN mod-97, BIC, currency, date/decimal facets), returning the extracted statement (message id, statement id, account IBAN/currency, balances, entries) on success or the structural error list on failure. Byte-identical extraction to the browser tool for the same input. Read-only parse -- feed the result to recon_match for reconciliation.
    ConnectorNo auth
  • List the saved payment methods (used only to pay for flight bookings, not for cards or adding funds). Returns each method with its id, brand, last 4 digits, and expiry, and marks the default one. Use setup_payment_method to add a new one. The gated tools set_default_payment_method and remove_payment_method also exist; call them by name even though they aren't in the tools list.
    ConnectorNo auth
  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Get analytics for a specific post (per_piece) or, when post_id is omitted, the agent-wide aggregate. Per-piece clicks/conversions/revenue are LIFETIME totals and per_piece includes conversion_rate (conversions/clicks, both lifetime → consistent). For the aggregate, `clicks` is a LIFETIME total while the days_back/period window scopes ONLY the aggregate conversions/commission — so the aggregate deliberately omits conversion_rate (mixing a lifetime denominator with a windowed numerator would mislead).
    ConnectorNo auth
  • Paid ($0.25, x402/USDC). Same full drift report as drift_report: every finding with file path, line number, what is wrong, and the suggested fix. Pay with x402 if you hold USDC; use drift_report to pay by card or other MPP methods.
    ConnectorNo auth
  • Get visitors grouped by browser name (Chrome, Safari, Firefox, Edge, and others), ranked by visitors descending, for a date range. Names only: use get_breakdown with dimension browser_version for versions, get_operating_systems for the OS split, and get_devices for desktop versus mobile. Pass filter_browser to other tools to scope them to one browser. Rows carry value, visitors, revenue, and percentage with pagination.total; limit defaults to 100 (max 1000). Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
    ConnectorOAuth
  • Use this when the user asks how a property's topic clusters perform: clicks, impressions, CTR (0-100), impression-weighted average position, matched query count and share of clicks (clickShare, 0-100) per cluster, plus an "unclustered" bucket for queries no cluster claims. Not for the cluster definitions: use list_topic_clusters (create_topic_cluster adds one). Pass clusterId to drill into one cluster's top queries (each row lists which of the cluster's keywords matched). A cluster keyword is a case-insensitive substring unless wrapped in slashes (/seo ?tools/), which makes it a regex. IMPORTANT: clusters may OVERLAP (a query matching two clusters counts fully in both), so cluster totals do not sum to the property total; `overlappingQueries` reports how many queries are double-counted. Shares are of visible queries only: `coverage.hiddenClicksShare` (0-1) is the share of the property's clicks with no query row. Clusters are listed by name; drill-down queries by clicks, highest first. Matching runs over the top `scanLimit` queries by clicks (default 50,000), read from the GSC Wizard ClickHouse warehouse when available (which scans at most 50,000 queries; `scanLimit` in the response is the limit actually applied), otherwise the live Search Console API (see `dataSource`). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
    ConnectorOAuth
  • Get a compound's interaction data: drug-drug interactions (DrugBank), drug-food interactions, and chemical-target interactions (binding/activity from BindingDB, ChEMBL, and others). Each entry carries its originating source. Results are paged per kind, with the source-record total and the next offset reported for each. Richest for approved drugs; many compounds have no deposited interaction records. Drug-drug and target interactions come from PubChem's SDQ service, which can refuse automated requests — a refused kind is reported in failedKinds while the others still return; per-target activity is also available from pubchem_get_bioactivity.
    ConnectorNo auth
  • Drug interactions come only from FDA drug labels: thorough for supplements labels name often (St. John's wort, grapefruit, magnesium, ginkgo) and sparse or missing for most others (e.g. fish oil, vitamin K, berberine, ashwagandha); read coverage.drug, and never treat an empty or short list as proof of safety. To check one medication pass drug (generic name; salt forms merged, so 'warfarin' matches 'warfarin sodium'; brand names are not matched). Also returns curated supplement-supplement interactions (synergies, antagonisms, absorption conflicts, timing), except on a drug check unless include_supplement_interactions is true. Interactions recorded for what the supplement contains are included and labelled: fish oil returns EPA, DHA and omega-3 interactions, turmeric returns curcumin's (interaction_sources, recorded_for). Drug entries are one per drug, most severe first, paged with drug_limit/drug_offset (drug_page.total, next_offset); label_artifact_suspected marks an entry whose drug name contains the supplement only as a salt (e.g. esomeprazole magnesium) and whose text does not mention it. Data-source failures return an error, never an empty list. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
    ConnectorNo auth
  • Drug interactions come only from FDA drug labels: thorough for supplements labels name often (St. John's wort, grapefruit, magnesium, ginkgo) and sparse or missing for most others (e.g. fish oil, vitamin K, berberine, ashwagandha); read coverage.drug, and never treat an empty or short list as proof of safety. To check one medication pass drug (generic name; salt forms merged, so 'warfarin' matches 'warfarin sodium'; brand names are not matched). Also returns curated supplement-supplement interactions (synergies, antagonisms, absorption conflicts, timing), except on a drug check unless include_supplement_interactions is true. Interactions recorded for what the supplement contains are included and labelled: fish oil returns EPA, DHA and omega-3 interactions, turmeric returns curcumin's (interaction_sources, recorded_for). Drug entries are one per drug, most severe first, paged with drug_limit/drug_offset (drug_page.total, next_offset); label_artifact_suspected marks an entry whose drug name contains the supplement only as a salt (e.g. esomeprazole magnesium) and whose text does not mention it. Data-source failures return an error, never an empty list. The supplement may be a name or an Aviado canonical_id (from search_supplements or a candidates list). Check status first: needs_confirmation / no_match means the input did not resolve, data is null and next_step says how to retry.
    ConnectorNo auth
  • Returns a deep-link URL that opens the map in the user's browser and automatically triggers a PNG download. The user clicks the link, the browser renders the map at full resolution with the legend composited (if legend: true), and the file downloads. There is no server-side rendering; the user's browser is the renderer. Required: map_id. Optional: format (png default), legend (true default).
    ConnectorNo auth
  • Open a W3C WebDriver session on the testing grid — a browser session (Selenium) or a mobile-device session, decided by what you pass: a browserName such as chrome, firefox or MicrosoftEdge for a browser; an empty browserName plus platformName ANDROID or IOS and a device UDID in capabilities for a device. Returns the sessionId every other session_* tool takes, and the capabilities the grid actually negotiated. This is the automation-protocol surface — reach for it when the work needs element handles or mirrors existing WebDriver code. To drive a desktop browser page without a WebDriver session use the web_* tools (addressed by pageId); to drive the browser on a real phone use the webpage_* tools (addressed by udid). Leave platformName and browserVersion off unless you must pin them: literal 'any' or 'latest' is strict-matched against node stereotypes, which advertise concrete values, and fails to match anything.
    ConnectorOAuth
  • List the pre-built xTiles workflows — curated, step-by-step recipes the team has prepared (recurring digests, weekly reviews, briefs, planner/space setup, onboarding, etc.). Call this FIRST — before you start assembling any multi-step process in xTiles by hand — whenever the user wants to set up, automate, schedule, recurring-ly produce, onboard, or "have xTiles do something for them", or asks what xTiles can do automatically. If there is any chance a prepared workflow already covers the request, check here before improvising with individual `xtiles_*` tools. Returns each workflow id, title, and when to use it — match the request to the closest entry, then call `xtiles_get_workflow` with that id to see the steps it suggests. If nothing matches, proceed normally with the other tools.
    ConnectorOAuth