Skip to main content
Glama
754,184 tools. Updated 2026-11-07 01:46

"An analytics platform for processing real-time data events" matching MCP tools:

  • Replaces the video or image behind a not-yet-published post (draft, ready, scheduled or failed) with another upload from the same workspace, like the dashboard's "Replace media". The post keeps its schedule, captions, first comments and platform settings; only the media file changes. Set `apply_to_batch: true` to also swap every other post in the same batch (same media, same status and, for scheduled posts, the same scheduled time), which is what you want when one upload was scheduled to several platforms at once. Upload the new file first with create_video_upload_from_url or create_video_upload + finalize_video_upload, then pass its id here. Refuses text posts, carousels, and posts that are queued, processing or published. Platform compatibility of the new file is not re-checked, so pick media that suits every platform in the batch.
    Connector
    Destructive
    OAuth
  • Get reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field. Covers 24 query types (marketSummary, accountState, orderbook, candles, topAddresses, whaleContext, etc.); `queryType` accepts exact, partial, or fuzzy names and returns params, response fields, example, weight, and freshness; `category` lists a group (queryType wins if both are supplied); omit both for the overview and rate-limit rules. Read-only bundled docs — it does not call the endpoint. Use instead of get_api_info for zero-auth public data; use get_api_info for authenticated trading, get_indexer_api_info for historical analytics, and get_strategy_vault_api_info for vault data.
    ConnectorNo auth
  • STEP 3 (mobile_money only, when initiate_payment returned instruction.action == "submit_otp"). Submits the one-time password the buyer received to authorise the mobile-money charge. REQUIRES the same buyer_delegation_token used for initiate_payment. After submitting, poll get_payment_status until payment_status is "paid"/"processing" or "failed".
    Connector
    Destructive
    No auth
  • Test how much a recorded birth time can actually be narrowed, and against what. Two modes: * **No events** — scans the uncertainty window and reports how many genuinely distinct charts it contains, what differs between them, and what does not. Use this FIRST to find out whether rectification is even worth attempting. * **With events** — scores each candidate against dated life events and checks the result against a null model of randomised dates. This tool does NOT return "your real birth time is X", and you should not present it that way. The unit of the answer is the **variant** — a group of minutes producing an identical chart structure. Preferring one minute over its neighbour inside a variant is fitting arithmetic, not evidence. Read `verdict.usable` before quoting anything else. Fewer than three independent, well-dated events fits the events rather than the birth time, and the verdict will say so. Args: dob, tob, tz, lat, lon: Birth data, as for create_chart. `tob` is the centre of the window, not an assertion. events: Dated life events, e.g. [{"date": "2015-06", "type": "job_change"}, {"date": "2019-03", "type": "marriage"}]. Dates may be YYYY-MM or YYYY-MM-DD. See `event_types` in the error response for the accepted vocabulary. half_width_minutes: Half-width of the uncertainty window (max 120). step_minutes: Candidate spacing in minutes. ayanamsha: Sidereal zero-point. Costs one full chart computation per candidate, with a minimum of 20 per call — a 30-minute window at 1-minute steps is 61 charts and takes a few seconds. The floor means a very narrow window is not cheaper than one considered call, which is deliberate: probing repeatedly is the wrong way to use this. On the shared public demo a single call is capped at 61 candidates; the refusal names two smaller calls that fit.
    ConnectorNo auth
  • Check a video run that returned status "processing". Pass its job_id exactly as given (it can be long: copy all of it). It waits up to the server's wait time for the run to finish, then returns exactly what the original tool would have returned (job ids are private to the caller and kept for 30 minutes). Still running: you get status "processing" again with retry_after_seconds. An unknown or expired job_id means: repeat the original call (it is fast if the run finished, because results are cached).
    ConnectorNo auth
  • Check a video run that returned status "processing". Pass its job_id exactly as given (it can be long: copy all of it). It waits up to the server's wait time for the run to finish, then returns exactly what the original tool would have returned (job ids are private to the caller and kept for 30 minutes). Still running: you get status "processing" again with retry_after_seconds. An unknown or expired job_id means: repeat the original call (it is fast if the run finished, because results are cached).
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Enables access to real-time news articles through search, topic headlines, full story coverage, and geo-based local news across multiple countries and languages using the Real Time News Data API.
    7
    MIT

Matching MCP Connectors

  • USCIS processing times per form and office, plus whether your case can file an inquiry yet.

  • Events with dates, venues, prices and organisers from Eventbrite and Meetup.

  • Link a GA4 property (properties/<id>) to a Google Ads account, so its key events can be imported into Google Ads as conversions and paid visits join the organic ones. customer_id is the Google Ads account (digits; hyphens are stripped). ads_personalization_enabled shares Analytics audiences and remarketing events with Google Ads — off unless the user asks for it. Read ga4_list_google_ads_links first: a property already linked to this account needs no second link. While linked, Google Ads click and cost data flows into this property and Analytics data flows to that Google Ads account; the link stays until someone removes it in Analytics (Admin, Product links), as this connector cannot unlink. Tools revision: d80f65c0.
    Connector
    Destructive
    OAuth
  • Get reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings. Omit both parameters for an overview with base URLs, categories, common errors, and usage tips; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its parameters, request/response schemas, and TypeScript example (category takes precedence if both are supplied). Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, dashboards, account history, and leaderboards; for live trading operations use get_api_info, and for zero-auth market data use get_public_info_api_info.
    ConnectorNo auth
  • Follow an `export_video` call that returned status "processing": pass its exportId. Waits up to waitSeconds (default 40) for the render, then returns status "ready" with the videoUrl, "failed" with the reason, or still "processing" with the render's progress (0 to 1): then call it again. Renders usually take 1 to 10 minutes; one still rendering after an hour fails with Timeout. Requires an active Revid plan.
    ConnectorOAuth
  • Get per-platform engagement (views / likes / comments / shares) as a time series over the trailing window_days (default 28, up to 365). Omit account_id to aggregate across all connected accounts, or pass one from list_accounts; optionally filter to a single platform. post_limit (≤100) fixes how many recent posts form the baseline. granularity buckets the series server-side ('daily' default, 'weekly', or 'raw' for every scrape). Read `series` (a clean per-platform list of typed points) — `metrics` is the legacy column/data matrix kept for back-compat. NB: follower counts here are latest-only; for audience growth over time use get_follower_history.
    ConnectorOAuth
  • Free legal-compliance check of a public website (no signup). Fetches the URL server-side and detects data processing relevant to compliance — analytics, marketing pixels, payments, generative AI, email collection, third-party sharing — then returns the legal documents and cookie-consent setup the site needs, whether the EU AI Act applies, and suggestedAnswers you can pass straight to generate_policies. Result contract: `fetched` is true only when the page HTML was actually read; when false, `fetchError` says why ("unreachable": the URL could not be resolved or connected; "blocked": the server answered with an error status) and the detected signals are NOT meaningful — report the check as inconclusive, not as clean. Run it again after adding any SDK, analytics, payment, auth or AI integration: when an appId is passed (or read from the installed LexVibe snippet) the result ALWAYS includes a `drift` key — status "in_sync", "outdated" (listing processing the hosted legal documents don't cover yet) or "unavailable" with a bounded `reason` (no-database, app-not-found, no-baseline, domain-mismatch, page-not-fetched) when the comparison could not be made; treat "unavailable" as unknown, never as in sync. Read-only.
    ConnectorNo auth
  • Get the latest intraday reading for active U.S. listings (consolidated SIP: last trade, UTC time, session freshness, bid/ask) and for listings named MIC:TICKER on a Canadian exchange (XTSE, XTSX, XCNQ, NEOE; e.g. XTSE:RY) or Euronext (XPAR, XAMS, XBRU, XMSM, XOSL, MTAA, XLIS; e.g. XPAR:AIR), in the listing's currency. Needs a paid plan: for U.S. listings Pro is real time and Plus 15 minutes delayed; Canadian readings are real time on XTSE and XTSX and 15 minutes behind on XCNQ and NEOE, and Euronext readings are the last trade 15 minutes behind (Delayed=true). Free covers end-of-day data only and gets an upgrade note. Stale=true means the reading predates the session expected now and must not be reported as current. Missing readings are listed. For settled daily bars use GetLatestClosingPrices or GetStockPrices.
    ConnectorNo auth
  • List the platform connectors set up on this Autario account: search, web and product analytics, ads, social, commerce, payments, AI usage and developer platforms. The answer names each connected platform, so call this instead of guessing which ones exist. Each entry carries its live dataset_id (queryable via query_dataset), datasets[] (ALL datasets the connector materialized | multi-report connectors produce one per report), refresh interval, last refresh time, and `health`: state (ok | stale | needs_sign_in | reports_missing | retrying | ours | never_ran | running), how old the data is per dataset, and next_step { who: assistant | user | nobody, action, url? }. CHECK health.state BEFORE answering from a connector table: ok = use it; stale = call refresh_connector once; needs_sign_in = give the user the one sign-in link in next_step.url, do not refresh; reports_missing = say which reports and why (get_connector_status has the per-report sentences); retrying or ours = answer from the data you have and say how old it is. Use this whenever a user asks about "my Search Console data", "my ad spend", "my store orders" or wants a cross-platform weekly report. Connectors are created and configured by the account owner in the Autario UI (autario.com/manage) | this tool only reads them, it never changes settings or handles credentials. Requires AUTARIO_API_KEY.
    ConnectorNo auth
  • Check for new accessible messages and creator-only join/security events, waiting at most 25 seconds. For authorized ongoing listening in a host that cannot maintain a stream, use its supported scheduler every 5 minutes by default; do not loop in the foreground or claim real-time delivery. Reads do not consume Tincan's shared-message quota. Returns an array of events: persist the last seq after recording pending work and pass it as after; retain the cursor on an empty result. Join requests require user review, never automatic approval.
    ConnectorNo auth
  • Use before signing an unsigned Solana transaction, not for a token mint alone. Provide a real unsigned Solana transaction serialized as base64, with optional signer and expected intent. Malformed input is rejected before payment. Simulation returns ALLOW, WARN or BLOCK with reasons and balance changes. Optional idempotency_key is random 32-byte base64url. A signed call waits up to 20 seconds for analysis and can settle without a key. If still processing, echo the unpaid job_id with the same proof and arguments when ready. get_job_result reports processing and retry_after_s for free; the result appears there only after settlement. Costs $0.01 USDC via x402.
    ConnectorNo auth
  • Metrics for this workspace's published posts. Returns a summary totalled across every published post (post count, overall totals, totals per platform), plus the newest posts in detail, each with one entry per platform it went to: impressions, reach, views, likes, comments, shares and saves. A metric is null when that platform does not report it; supported=false means nothing can be read for that target (no analytics for the platform, or no post id yet). Values are the last stored reading, not a live fetch, and fetchedAt says when it was taken. Use this to answer whether posts worked. It covers published posts only: use list_posts for drafts and scheduled posts, get_post for one post's details, and get_link_in_bio for visits to the link-in-bio page.
    ConnectorAPI key
  • List Agentropolis platform features with status (live, partial, stub, planned), endpoint and guardrails: badges, the x402 relay, seller claims and analytics, sponsored placement, market data, billing. Use it to check whether a platform capability exists before relying on it; it describes Agentropolis itself, not listings. Read-only, no parameters. Stub endpoints answer HTTP 501; payments_enabled shows whether Agentropolis charges for anything (currently false).
    ConnectorNo auth
  • Estimate how real up to 20 creators' followers are, from public views, engagement, likes and following. Creator ids must come from this user's searches (pass search_id), lookups or saved creators. The first checks each day are free (see get_account), then 5 credits each; creators without enough data cost nothing; results from the last 7 days are reused for free unless fresh=true. This is a rule-based estimate, not platform data; present it that way.
    ConnectorNo auth
  • Refreshes a workspace's post analytics (views, likes, comments, shares, account stats) from the connected platforms. Same operation as the Sync button on the ShortSync Analytics tab. Runs in the background and returns a job_id right away; a sync takes roughly 15 seconds to 5 minutes. Pass job_id (with the same workspace_id) to check progress instead of starting a new sync: status goes queued → running → completed/failed, and the analytics read tools return fresh numbers once it is completed. The read tools (get_workspace_analytics, get_post_analytics, get_video_analytics, get_folder_analytics, explain_post_analytics_state) already start a sync on their own when the data is over an hour old, so only call this when the user explicitly wants a refresh now. Only one sync runs per workspace at a time. Counts against the workspace's daily sync limit; Free plan workspaces can sync once per calendar month.
    ConnectorOAuth
  • Start an Ad Platform Export: push a list's Online Audience to the user's connected ad account as an Ad Platform Audience. Not billed. Find the platform, `account_id` and, to add to an existing Ad Platform Audience, its `audience_id` with `ads_export_options`. Pass `audience_name` to create a new Ad Platform Audience instead. The export runs in the background; check it with `ads_export_status` and the returned `history_id`. Only one export of a list to a platform runs at a time. When one is already running, no new export starts: `already_in_progress` is true and the response describes the running export, whose account and audience may differ from this request.
    Connector
    Destructive
    OAuth
  • Get the next open queue time for each platform named: the time queue_post would give a post now. Times are ISO 8601 in the workspace's posting time zone. Already booked and penciled times are skipped. A platform with no channel says no_connected_account. A platform with more than one channel lists them; pass platform_account_ids to pick one. "no slot configured" means that channel has no posting times yet (add them with add_queue_times). For the whole weekly schedule, use list_queue_schedule; for posts already booked, use list_scheduled_posts.
    ConnectorOAuth