Skip to main content
Glama
800,533 tools. Updated 2026-11-18 15:59

"Access GEO Biomedical Datasets" matching MCP tools:

  • Set a campaign's WHOLE geo-targeting set in one call — named areas and radius circles in a single include/exclude list, plus the campaign-level presence-vs-interest choice — the easy front door over update_campaign's geoTargets. Place names in include/exclude are resolved server-side (countries → geo registry → Google suggest); radius entries take lat/lng or an `around` place name (geocoded). Radius rows can only be INCLUDED (neither platform supports negative proximity — carve out places with an excluded area instead), and a set where every row is negative is rejected (ONLY_EXCLUSIONS). An empty set is legal: no geo criteria = ads can serve anywhere. locationIntent defaults to PRESENCE (people actually in the locations) — deliberately NOT the platforms' wider search-interest default. Use dry_run:true to get the resolved rows + the plain-language effective-targeting sentence (exactly what the UI shows) WITHOUT mutating the campaign. Scoped to the active Space.
    ConnectorAPI key
  • Manage a Google Ads campaign or ad group's targeting AFTER creation: GEO, LANGUAGE and AUDIENCES. op 'add' at campaign level (default): up to 100 locations (negative: true = exclude) and/or 50 languages, OR up to 50 audiences (audiences cannot combine with geo/languages in one call — separate calls). op 'add' at ad-group level (level: 'ad_group' + ad_group_id): audiences only. AUDIENCES: pass user_list_id items (audience segments from adsap_google_list_audiences) — campaign-level TARGETING works on Search/Shopping only; campaign-level EXCLUSION (negative: true) also on Display/Performance Max; ad-group level (target or exclude) on Search/Display/Shopping. DEMAND GEN is different: pass audience_id items (Audience resources) on the AD GROUP — nothing at campaign level. Video supports no audience edits. The same user list cannot be attached at BOTH campaign and ad-group level. 'mode' ('targeting' = narrow delivery to the audiences | 'observation' = full reach, bid adjustments only) sets the audience targeting setting — combinable with the audience add or standalone; Google's default with NO mode set is TARGETING, so pass mode: 'observation' for Search/Shopping unless the user explicitly wants to narrow reach. op 'remove': remove ONE criterion by composite id "<parent_id>:<criterion_id>" (level 'campaign' → campaign criterion, 'ad_group' → ad-group criterion). Geo/language criterion ids EQUAL their constant ids (France on campaign 123 = "123:2250"); AUDIENCE criterion ids are Google-internal — capture them from the add response (created_criteria[].entity_id). Criteria are immutable: to change one, remove it and add the replacement. Always dry_run: true first. For campaign negative KEYWORDS use adsap_google_manage_keywords op 'add_negative'.
    ConnectorAPI key
  • Query the verified share of US manufacturing plants USING industrial robots — plus workers exposed and robotics capex — from the Census Industrial Robotic Equipment product (the first official federal robotics-adoption statistics). Use this for "are factories actually adopting robots" questions — the INSTALLED-BASE reading the import data cannot see. Serves the percent of plants with robots and the percent of employees at plants with robots (both published as FRACTIONS of 1: 0.121 = 12.1%), Census's demeaned variants, and capital expenditures for robotic equipment ($1000) — by manufacturing industry (`naics_code`, 2/3-digit), by `state`, and by `plant_size` band. Filter by `edition` ("asm_2018_2021" = the ASM annual series; "ec_2022" = the 2022 Economic Census), `table` (the workbook sheet — exactly one of: "Percent of... NAICS", "Percent of... Geo", "Percent of... Geo demean", "Robot adopters vs not", "Robot adoption and plant size", "CapEx... NAICS", "CapEx... Geo", "CapEx and plant size"), `data_year` (2018-2022), `naics_code`, `state`, `plant_size`, or `geo_area_name` ("United States" for the national row). Group by any of `edition`, `table`, `naics_code`, `naics_title`, `state`, `plant_size`, `data_year`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"table": "Percent of... Geo", "data_year": 2022, "group_by": ["state"], "order_by": "avg_pct_plants_with_robots", "top_n": 10}` for the most-automated states; `{"table": "Percent of... NAICS", "edition": "asm_2018_2021", "naics_code": "336", "group_by": ["data_year"]}` for transportation-equipment adoption over the ASM years. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every value cites its exact workbook cell-group, re-verifiable via get_source_evidence_v1. THE ENGRAVED BOUNDARY: the two editions are NEVER spliced into one trend — the 2022 Economic Census reaches the small-plant universe the ASM sample does not (US plants-with-robots: 12.1% ASM-2021 vs 6.4% EC-2022 — a COVERAGE change, not a decline; every cross-edition scope carries an edition_scope note). Percents are INTENSIVE shares: avg/min/max over a scope, never summed. Capex sums UNDERSHOOT below the published totals wherever suppression bites (the published "United States" / "31-33" rows are the totals). Suppressed cells (D/S/A, decoded by the file's own footnotes) are null values with their verbatim letter — never zero; (s)-flagged estimates (standard error > 40%) carry their flag. Manufacturing plants only; adoption SHARES and capex, never robot counts (no official count of installed robots exists — the import unit-count series is query_robotics_trade_v1); an EXPERIMENTAL Census product (its own label); no edition after 2022 exists.
    ConnectorNo auth
  • Devuelve la definición de un término de SEO, GEO o búsqueda con IA del glosario de Autoridad Digital (25 términos en español, cada uno con URL citable). USAR CUANDO: preguntan «qué es X» o necesitas definir un concepto: GEO, AEO, LLMO, E-E-A-T, llms.txt, RAG, NavBoost, AI Overviews, entity SEO… NO USAR PARA: guías, análisis o casos sobre un tema (usa buscar_articulos) ni términos ajenos al SEO y la IA. DEVUELVE: nombre, categoría, definición corta citable, definición ampliada, slugs de términos relacionados (se pueden pasar en `termino`) y URL de la ficha. Si la definición no basta, busca el mismo término con buscar_articulos. SI HAY VARIOS O NINGUNO: no es un error. Si el texto encaja con varios términos («authority») devuelve `encontrado: false` y `candidatos`: elige uno y vuelve a llamar con su slug. Si no encaja con ninguno devuelve `disponibles`, la lista completa, así que no hace falta otra llamada para descubrirla. LÍMITES: ninguno; no hace peticiones externas.
    ConnectorNo auth
  • Pro-tier. Fetch and analyze a web page, then audit it against the Proximens GEO Engine principles across all major GEO dimensions (structured data, crawler access, content depth, freshness, E-E-A-T, multimodal). INPUT: url (required, http/https); optional mode ("fast" = quick signal checks, returns in seconds — the default; "deep" = a full AI-synthesized consultancy report in Dutch with a 7-dimension scorecard and sector benchmark, takes ~30-50s), client_name (report header), branche_hint ("main:sub", e.g. "health_wellness:yoga_studio"), max_issues (1-25, default 10). RETURNS: JSON with a 0-100 score, severity-ranked issues (critical/major/minor) each with a finding and an actionable suggestion, top recommendations, and a markdown report; deep mode additionally returns score_set (7 GEO dimensions), sector (benchmark cohort), and a full consultancy-grade report_markdown (deep_mode="timeout_fallback" with gedeeltelijk=true means the synthesis did not fit the ~50 s budget and the fast, deterministic result was returned instead; deep_mode_reden says why). status="blocked" (login/SSO, HTTP 401/403, bot-challenge) or "unreadable" (no readable text) means NO report was generated — the reason is in error and blokkade. USE fast mode for quick checks and bulk triage; USE deep mode when you need a client-ready audit report. Free tier is blocked.
    ConnectorNo auth
  • Search a curated registry of 45 UK open datasets and APIs for property and neighbourhood research. Each entry records the dataset's home page, its machine-readable endpoint, format, licence, geographic coverage, update cadence, and the concrete questions it can answer. Use it to find the right source for something this server does not report directly — EPC ratings, planning applications, flood risk, council tax bands, bus timetables, air quality, ground stability, land ownership. Args: - query (string, optional): free text over name, publisher, category, endpoint and questions - category (string, optional): category prefix, e.g. "Crime", "Transport", "Environment" - limit (number): 1-45, default 10 - offset (number): pagination offset, default 0 - response_format ('markdown' | 'json'): default 'markdown' Returns: { total, count, offset, has_more, next_offset, datasets: [{ id, dataset, publisher, category, api, licence, coverage, update_frequency }] } Examples: - "Where do I get EPC data?" -> query="EPC" - "What flood datasets are there?" -> query="flood" - "List every transport source" -> category="Transport", limit=20 Follow up with postcode_get_dataset for the full entry including API docs and the questions it answers.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI Engine Optimization (AEO) and Generative Engine Optimization (GEO) audits, including llm.txt compliance, content stickiness analysis, and schema validation through natural language.
    MIT

Matching MCP Connectors

  • Onsite technical GEO visibility tests, score trends, sitemap discovery, and domain monitoring to ensure AI crawlers can access your site.

  • TradeHouse Datasets + Derived-Analytics API (calibration-as-a-service). Our own derived aggregates a

  • Obtains the complete list of Idescat statistics (all, normalized and non-normalized). It has no parameters. The response contains a 'statistics' array where each element has: 'acronym' (lowercase acronym, e.g., 'censph', to be used as the 'stat' argument of the other tools), 'name' (title), 'description' (summary), 'datasets' (boolean), 'geo' (array of available territorial disaggregations), and 'url' (initial web address, relative to https://www.idescat.cat). Use it when the user asks what statistics are available or when a statistic needs to be found by name or territorial disaggregation. THREE KEY FIELDS to decide the flow: (1) 'datasets' — if true, the statistic is normalized and you can use the rest of the tools (get_idescat_stat_tables, get_table_metadata, get_table_data, get_table_geo, render_table); if false, ONLY the information from this tool and get_idescat_stat is available. (2) 'geo' — available levels of geographical disaggregation (e.g., 'cat'=Catalonia, 'prov'=provinces, 'at'=territorial plan areas, 'com'=counties and Aran, 'mun'=municipalities, 'dis'=districts, 'sec'=census sections). ALWAYS CHECK 'geo' before choosing a statistic for a territorial query: if the user asks for county data, choose a statistic that includes 'com' in 'geo'. (3) 'url' — home page of the statistic on the Idescat website. POPULATION FIGURES: when population data is requested, there are several sources: the main and richest is CENSPH (population and housing census, annual); for semi-annual estimates there is EP (population estimates, semi-annual); and there is also PMH (municipal register of inhabitants, annual). By default, choose CENSPH (or EP if semi-annual data is requested) and NEVER use PMH for population data unless the user explicitly asks for it.
    ConnectorNo auth
  • Compare 2-5 named products or services on Nigeria-usability: naira pricing, card acceptance, local entity, geo-restriction. Rows are returned in the order given — Ranked does not rank them here. Ranked Technologies operates some listed products; those carry operated_by_ranked=true, are returned in a separate unranked block, and are never ordered above others (Rule 1). Evidence tier is provenance, not quality.
    ConnectorNo auth
  • Google Trends related topics for a keyword. Returns the topics and named entities associated with a keyword in a given country, as top topics scored 0-100 relative to each other and rising topics with percentage growth, each carrying its entity type. Google Trends topic discovery for market research and content planning. [$0.03/call]. Params — keyword: the search term; geo: ISO-3166 alpha-2 country code, e.g. US, GB, DE, JP (213 countries supported); timeframe: time window. Each response reports its own bucket size in `granularity`: past_30_days and past_90_days return a daily series, past_12_months and past_5_years weekly, windows under a day hourly (2004_present|past_12_months|past_30_days|past_4_hours|past_5_years|past_7_days|past_90_days|past_day|past_hour) Example params: {'keyword': 'bitcoin', 'geo': 'US'}
    ConnectorNo auth
  • Find what official data is available about a topic. Use this to explore what datasets exist. It returns catalogue metadata, never observations — and neither do ``ask`` and ``build_url``, which prepare an exact source request that still has to be downloaded and queried (``fetch`` / ``stage_url`` when the client cannot do that itself). **Two response shapes**, and ``shape`` says which one arrived. - ``ranked`` — ``results`` lists matching datasets, best first, each with its dimensions, coverage, and the ``matches`` that justify it. - ``anchored`` — ``topic`` named one concrete code (a place, a country, an indicator) and nothing forced the ranked path. The answer is then ``anchor`` (the code chosen, and what else the topic could have meant), ``facets`` (what varies across the datasets publishing it) and ``anchored_datasets`` (those datasets, paged by ``page.next_offset``). ``results`` is ``[]`` on this shape by construction — that is not "nothing found". If the chosen code is wrong, re-query with one of ``anchor.alternatives[].name``. The two shapes never both appear. Anything that scopes the search is served by the ranked path: ``agencies``, ``region``, ``user_country``, ``keywords``, a non-English ``language``, or an ``offset`` past the anchored page. A code also stays ranked when fewer than max(15, ``limit``) datasets publish it (it or a code beneath it), and when resolving it or counting its datasets fails or does not finish in time — that last case, and only it, carries a ``retrieval_degraded`` warning with level ``anchor_unavailable``; a retry may then anchor. Anchored rows are datasets that publish the code or one beneath it — never ones merely permitted to carry it, never ones carrying only its parent. Two keys explain the rest of the response: ``_k`` expands the abbreviated row keys, and ``_notes`` explains whatever this particular response happens to contain, keyed by field or ``field=value``. Common workflow: discover -> inspect -> ask
    ConnectorOAuth
  • Duplicate an existing Meta ad set into 1-10 copies, keeping ALL its ads (including ads with no delivery yet). Every copy and every recreated ad is PAUSED. Each recreated ad reuses the source ad's creative, so the original post and its likes/comments are preserved. Per copy you can override the name, the geo targeting (geo-split flow: one copy per region/country) and daily spend limits — as absolute amounts or as a % of the campaign daily budget (Advantage campaign budget campaigns only; the % auto-computes the absolute like Ads Manager). ALWAYS call with dry_run: true first: it returns the plan (source ad set, the exact ads that will be recreated, per-copy overrides, warnings) — show it to the user and only execute after they confirm. Partial failures are reported per copy and per ad in data.copies[].errors with Meta's own error text.
    ConnectorAPI key
  • Measure a public https dataset URL and return its exact sizeBytes, sha256 and contentType, plus suggestedEntry — a filled-in element of the spec's datasets[] array you can paste straight in. Call it before submitJob whenever you want datasets[] to stage and verify a file: sizeBytes and sha256 are REQUIRED on every entry, and this is how you get them without pulling the data down to your own machine first. We read the URL from our side, stream it through a hash and keep no copy. Free, books nothing, and it never reads the caller's filesystem. https only, and only addresses on the public internet: a loopback, private, link-local or otherwise reserved host is refused, and so is a redirect that leads to one. There is an upper size limit and a limit on how often one session may call it; both refusals say so plainly. You do NOT need this when your command downloads its own data with curl or wget — datasets[] is the verified-staging path, and only that path needs a hash declared up front.
    ConnectorOAuth
  • Run a fresh GEO Audit of the client's website now and save it: AI-crawler access (robots.txt, and whether test requests with each crawler's name were refused, a sign of a block, not proof), llms.txt, structured data, content and technical checks on the homepage and sampled pages, Agent Readiness (preconditions only, not a task test), and AI-written insights. It audits the website set on the client, not an arbitrary domain, uses none of the workspace's scan allowance, and can take a minute or more. One audit per project per 15 minutes. Without confirm:true it returns a preview; get_geo_audit returns the full result.
    ConnectorOAuth
  • Copy an eligible public dataset and its runnable data collection pipeline into a new free workspace. Select organisation_id from get_context when more than one is available. Requires authenticated organisation access. Copies the entire existing snapshot without collecting fresh data or charging imported rows; 100 free collection rows remain and schedules start disabled. Returns workspace_id, dataset_id, pipeline_id and a browser URL for immediate query_dataset, browse_dataset_rows or export_dataset use. Use the source dataset public ID and a new UUID idempotency_key; reuse both on retry to return the same workspace. No setup, build_workspace or accept_workspace step is needed. Directory publication authorizes copying linked datasets in the source workspace, including uploaded inputs. Saved site logins are unsupported. Future run_pipeline calls use the usual estimate and confirmation flow.
    ConnectorOAuth
  • [Trading Data API] Hyperliquid perpetual context: funding (hourly), open interest, mark/oracle/mid price, premium, 24h volume. Not geo-blocked. **Example:** `/v1/hyperliquid?symbol=BTC` Use when you need Hyperliquid perp context: funding, open interest, mark/oracle price, premium and volume. Not for Binance/Bybit aggregates (use funding_oi). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).
    ConnectorNo auth
  • Numbers over what was collected, never rows (rows are super_data). Aggregate `measures` across the datasets in `scope`; datasets combine on the same measure in one base unit, results in the declared `unit`. Names come from the catalog; an unknown one errors with near misses. The answer has one row per `group_by` key (or one row) with a column per measure and `compute`, the datasets used and any skipped, and `truncated` when `limit` cut it. Or send `distributions` for one artifact: counts, per-version rates and per-field distributions (free text: answer rate and length only). A call with neither is `invalid_query`.
    ConnectorOAuth
  • Inspect sources, preview a read-only request, or save a new dataset. Requires team-admin access to all projects. Inspect without connectionId lists connections; with it, lists source resources. Preview requires connectionId and SQL query or MCP configuration. Save also requires name, projectId, and datasets:write; it executes the preview again and creates a dataset only with usable rows. Repeated saves create new datasets. Unsupported sources must be explored in Chartbrew. Use run_dataset for existing datasets; never infer field meanings from names.
    ConnectorOAuth
  • Change the access of a saved test (permission: edit) Sets or removes the saved access of a protected website test (https url only; any other test is 400 field_not_applicable on access). `access` as an object replaces the saved access whole: basicAuth { username, password } and/or up to 3 headers (never Host, Cookie or Authorization), sent only to the origin of the test's url by every scan, journey recording and replay; a header left out is removed and basicAuth needs its password again. `access: null` removes it. Write-only: the values are never returned; the 200 is the Target with only `access.basicAuth` and `access.headerNames`. Starts no scan: the next scheduled scan or POST /targets/{id}/scans uses it. URL, country and type cannot change. The values pass through you once and are never returned: get_target and the dashboard show only access.basicAuth and access.headerNames. To check the access, start a scan with rerun_target_scan; get_scan answers accessFailure when the site still refuses it.
    Connector
    Destructive
    OAuth
  • Run read-only JavaScript to analyze project data — use this instead of paging large datasets through query tools when a question involves aggregation, joins across entity types, or more than a page of records. The code runs in Telerivet's Cloud Script API sandbox (synchronous JavaScript) with the `project` global set when a project is bound (undefined in organization-only runs with no project_id), plus an `organization` global for organization-level data (billing details and transactions, usage, the organization's projects) — organization methods work only where the user's own permissions allow. Write top-level statements — do NOT wrap the code in a main() function — and end with a top-level `return <value>` returning a compact JSON-serializable result (counts, samples, summaries — never full datasets); use console.log(...) for progress output. Each run has limited execution time and API requests (12 seconds / 250 requests unless the project's admin settings allow more): prefer cursor.count() and filtered queries over scanning every record, avoid one API call per record, and bound big jobs with cursor.limit(n), processing one segment per run. The result's 'usage' property reports usage against these limits, for sizing batches across runs. For genuinely large bulk operations, create an asynchronous batch task instead (project.createTask, or the Project_createTask API method), which processes all matching records server-side without these limits. Use get_method_schema for JavaScript example code for a specific method, and call get_documentation with id 'cloud_script_api' for the Cloud Script API reference — check it before writing nontrivial code rather than guessing method signatures. This tool's API access is READ-ONLY: methods that create, update, send, or delete fail, and HTTP requests are disabled. To perform changes, use run_script instead.
    ConnectorOAuth
  • Get the link to create a ThinAir GEO (geocoding/routing) API key. Returns console_url (the signed-in ThinAir Geo console) and instructions; it does NOT return a key and does not create, rotate or revoke any key. The owner signs in, creates the key there and sees it once in their own browser, then sends it as an Authorization: Bearer header. Existing keys keep working. Counts as 1 query against your daily quota. NOTE: keys created there work ONLY against ThinAir Geo — they do NOT authenticate against ThinAir Data, which issues its own ta_data_* keys from its own identically-named tool.
    ConnectorOAuth
  • List available connectome datasets with their labels and symbols. Use the returned symbols when constructing exclude_dbs arguments for query_connectivity. Common datasets include Hemibrain (hb), FAFB (fafb), MANC, and others. Call this tool if unsure which dataset symbols are valid.
    ConnectorNo auth