Skip to main content
Glama
633,357 tools. Updated 2026-10-03 12:25

"Tools for Enhancing Browser Functionality or Performance" matching MCP tools:

  • Returns trimmed Code IQ automated analyses (architecture, scalability, EOL, AI functionality, etc.) for a project (aggregated) or a single vault. Excludes The Code Score — use get-the-code-score for that, and do not pass analysis_key=code_score here (404). Only cached results are returned; this never triggers a fresh analysis. Provide exactly one of project_id or vault_id. Requires full data access (a paid plan; verification-only plans are not included). Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
    ConnectorNo auth
  • [RECEIPTS] Backtest performance over last N days (1-365, default 30). Same data as REST /performance. Note: no asset filter — performance is aggregated across all assets. Performance is the live forward-return record by signal type. DENOMINATOR CONTRACT — every block (overall, by_signal_type, by_coin, by_source) carries total/wins/partials/losses/expired/settled/win_rate. `total` counts signals emitted, settled or NOT: most expire unsettled, so wins/total is not a win rate and ranks lanes backwards. `win` = full take-profit only; a partial is not a loss. Rank on win_rate (wins/settled) or avg_pnl. `win_rate` is null when settled=0 — that is 'not yet measurable', NOT zero. For the gated per-type verdict with confidence intervals and the tradeable badge, use get_proof instead.
    ConnectorNo auth
  • [RECEIPTS] Backtest performance over last N days (1-365, default 30). Same data as REST /performance. Note: no asset filter — performance is aggregated across all assets. Performance is the live forward-return record by signal type. DENOMINATOR CONTRACT — every block (overall, by_signal_type, by_coin, by_source) carries total/wins/partials/losses/expired/settled/win_rate. `total` counts signals emitted, settled or NOT: most expire unsettled, so wins/total is not a win rate and ranks lanes backwards. `win` = full take-profit only; a partial is not a loss. Rank on win_rate (wins/settled) or avg_pnl. `win_rate` is null when settled=0 — that is 'not yet measurable', NOT zero. For the gated per-type verdict with confidence intervals and the tradeable badge, use get_proof instead.
    ConnectorNo auth
  • Start the device-flow authorization to attest works in this session (up to 20 attestations, 24h). Returns a link the USER must open in a browser and approve (anti-bot check included). After the user approves, call `complete_authorization`. Not needed if the connection already carries an API key header, or for verification tools.
    ConnectorNo auth
  • Fetch one fund's metadata by ticker (`code`): name, type (ETF or FUND), exchange, currency, ISIN, active/inactive status, and the date range for which return data exists. Returns 404 if the ticker is unknown. Use searchFunds to resolve a name to a code; use the returns tools for performance.
    ConnectorNo auth
  • Query the caller's own account CONTEXT from the Metadata.io knowledge base — a rolled-up summary (firmographic, recent 90-day campaign history, open drafts, per-experiment performance) refreshed overnight. Use it to GROUND a recommendation or plan in the account's own history before you suggest or generate something. USE FOR: firmographic (industry, size, revenue, country) and high-level recent-history context to back a decision — e.g. "given our recent LinkedIn performance, what should we try next quarter?". NOT FOR the account's CURRENT LIVE STATE. This is a periodic roll-up, not the live platform — it can miss or misreport granular state (e.g. answer "nothing runs in Germany" while many live campaigns target Germany). For "what's running / what's live", "which campaigns target <country/segment>", "list our campaigns / audiences / offers", or real-time spend / pacing, use the live platform analytics tools instead (`account_level_stats`, `performance_metrics`, `demographic_country_stats`, `search_campaigns_by_names`, etc.). Also NOT FOR industry benchmarks (use `query_metadata_analytics_benchmarks`) or a different company (cross-tenant queries are rejected). The caller's `account_id` is resolved server-side from the credentials the call acts as. It cannot be supplied or overridden by the caller.
    ConnectorAPI key

Matching MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    Gives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.
    8
    -
  • A
    license
    B
    quality
    B
    maintenance
    A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.
    52
    223 npm
    3
    MIT

Matching MCP Connectors

  • performance-review MCP — wraps StupidAPIs (keyless — no credential needed)

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

  • Reads and tool lookup for Meta Ads; nothing called here changes anything. The 16 Meta Ads tools that change something run through meta_ads_write. meta_ads(action="execute", tool_name="…", arguments={...}). action="list_tools" (the write half included) and action="get_tool_schema" are free; never guess a tool_name. accounts=["…","…"] or accounts="all_active": one read across up to 20 Meta Ads accounts, free like every read. Not in this router, called by name: meta_get_campaign_performance (meta campaign performance). Tools by category: **analysis** meta_analyze_audiences, meta_analyze_wasted_spend, meta_detect_creative_fatigue, meta_get_audience_insights, meta_optimize_budget, meta_optimize_placements **targeting** meta_browse_targeting, meta_get_ad_set_delivery_estimate, meta_get_ad_set_targeting, meta_search_targeting **diagnostics** meta_explain_anomaly, meta_validate_creative_url **assets** meta_get_ad_creatives, meta_list_instagram_accounts, meta_list_media, meta_list_pages, meta_list_promotable_apps **performance** meta_get_ad_performance, meta_get_adset_performance **structure** meta_get_lead_form_submissions, meta_list_ad_sets, meta_list_ads, meta_list_campaigns, meta_list_lead_forms **audiences** meta_list_custom_audiences, meta_list_saved_audiences **conversions** meta_list_pixels
    ConnectorOAuth
  • Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.
    ConnectorAPI key
  • Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.
    ConnectorAPI key
  • Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.
    ConnectorAPI key
  • Get multiple Instagram posts by IDs (1-50 IDs per request). Returns results directly. Returns only found posts, omitting not-found IDs for flexibility. First searches database, then external API for missing/stale data in parallel. Use when you have multiple exact post IDs. NOT for search - use getInstagramPostsByKeywords. PERFORMANCE: Much more efficient than multiple single-ID calls. Batches database queries and parallelizes API calls. IMPORTANT: postIds must be in strong_id format (e.g., "3606450040306139062_4836333238") - use the full "id" value from other Instagram tools, NOT just the media_id. To find a post from an Instagram URL (e.g., instagram.com/p/ABC123/), extract the shortcode from the URL path and use getInstagramPostsByKeywords to search, or ask the user for the post ID. Optional fields parameter for performance: ["id", "caption", "likeCount"]. Returns: results array with id, caption, userId, username, createdAtDate, engagement metrics, count, dataSource. This is a safe, read-only tool for analyzing searchable information.
    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
  • FREE — check your own MCP credits wallet balance (the same account paid tools like assess_property_hazard charge against). Requires Authorization: Bearer <api_key> — an agent can call this on its own, no browser/dashboard needed. Returns JSON: {ok, balance, eur_equivalent} or {ok: false, error} if no API key was provided.
    ConnectorNo auth
  • Lists every performance of a single title, ordered by date, optionally narrowed to one city and a date range. Use this when the user asks for all dates of a title, or for its dates in a given city or on a given weekend - search_events returns only the nearest performance per title. Each performance carries its own venue, date, price, free places and buy_url. Only future performances are returned unless date_from says otherwise.
    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 before interpreting a performance or signal claim, especially when a user asks for assumptions, limitations or possible bias. Explains how the engine decides, what the published numbers do and do not claim, and the known biases in the record. Read this before quoting any statistic from the other tools.
    ConnectorNo auth
  • Use this before selecting a web-search, URL-fetch, browser-automation, cloud-browser, headless-browser, Playwright/CDP, or authenticated-browser provider. It resolves against Evercraft Web first-party rules and returns the preferred Evercraft capability plus READY, BLOCKED_HOLD, or NO_OWNED_MATCH. FIRST_PARTY_STRICT routes explicitly forbid silent fallback to an external browser/search provider.
    ConnectorNo auth
  • Reads and tool lookup for LinkedIn Ads; nothing called here changes anything. The 17 LinkedIn Ads tools that change something run through linkedin_ads_write. Naming: these tools use LinkedIn API names. Since October 2025 Campaign Manager calls a campaign group a "campaign", a campaign an "ad set" and a creative an "ad", so campaign_group_id is what the user sees as a campaign and campaign_id is an ad set. When the user says "campaign", check which level they mean (linkedin_get_campaign_structure shows both), and answer in the words Campaign Manager uses. linkedin_ads(action="execute", tool_name="…", arguments={...}). action="list_tools" (the write half included) and action="get_tool_schema" are free; never guess a tool_name. accounts=["…","…"] or accounts="all_active": one read across up to 20 LinkedIn Ads accounts, free like every read. Not in this router, called by name: linkedin_get_campaign_performance (linkedin campaign (ad set) performance). Tools by category: **analysis** linkedin_analyze_creative_performance, linkedin_analyze_wasted_spend **targeting** linkedin_estimate_audience_size, linkedin_forecast_campaign_supply, linkedin_search_targeting **discovery** linkedin_explain_objectives, linkedin_get_organizations **audiences** linkedin_get_audience_insights **structure** linkedin_get_campaign_structure, linkedin_list_campaign_groups, linkedin_list_campaigns, linkedin_list_creatives **performance** linkedin_get_creative_performance **reporting** linkedin_get_engagement_metrics **conversions** linkedin_list_conversions **assets** linkedin_validate_assets
    ConnectorOAuth
  • Pre-adoption decision tool for open-source reuse. Call BEFORE implementing non-trivial functionality that a maintained OSS component could provide (queue, scheduler, parser, auth, cache, protocol client, ...) or before adding a dependency. Send a short capability need plus your project's minimal constraints; returns up to 12 candidates by default (up to 20 when max_candidates is provided), with per-constraint pass/fail/unknown, evidence basis (observed vs inferred), and explicit no-hit semantics.
    ConnectorNo auth
  • Use this when the user asks whether GitHub, GitLab, Bitbucket, or Azure DevOps is connected, or asks which imported repository records already exist. Read-only: returns provider status and browser-only connect/reconnect guidance without exposing credentials. Use repository-link tools for Space Autopilot links.
    ConnectorOAuth
  • Aggregated performance snapshot for one container over a date range. Fast — hits the pre-aggregated reporting endpoint, not the raw events table. USE WHEN the user asks: - "How is my site performing last week?" - "How many events / what's the total value / how many emails collected?" - "What's my recovery rate / how many ad-blocked events?" - "Quick breakdown by traffic source" Returns totals, consent stats, recovery (adblock + restricted-browser) stats, and a per-source breakdown — all in one call. This is the DEFAULT first call for any single-period performance question. Only escalate to get_report when the user wants a breakdown by a specific dimension (event_name, day, hour, device, browser) or a time series. Date range required, max 30 days.
    ConnectorOAuth