Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-12USmethodology registry-public-v1
Searchable tools
113,018
Authless tools
7,424
Auth required
100,766
Described tools
61,167
113,018 tools
- Get account billingget · Billing detail for the account named by `account_id`: paid/outstanding QuickBooks invoices, recorded payments, and the per-feature usage rows that drive overage billing. Subaccounts of a parent are billed at the parent, so calling this on a subaccount typically returns empty invoice/payment arrays.FaradayFaraday
PluginrequiredData & Analytics - Get account dependency graphget · Retrieve the full dependency graph for the account — every edge between Connections, Datasets, Atlases, Streams, Cohorts, Outcomes, Persona Sets, Recommenders, Scopes, Targets, Places, Traits, Attributes, and Market Opportunity Analyses. Use this to orient on an existing account, understand how a use case is assembled, answer what a change or lifecycle action would affect, or plan an unblocking sequence before deletion. Each edge has `upstream_*` and `downstream_*` fields with id, literate name, type, status, archive timestamp, and the timestamps of last config edit, input read, and output write.FaradayFaradayPluginrequiredData & Analytics
- Get account overviewget · The foundational context for the account named by `account_id`: who the client is, what they do, the challenges they face, and the future state Faraday is helping them reach. It is the account-level framing that the individual use cases sit within. The overview is markdown and can be empty (a fresh account with nothing written yet returns `{ content: "" }` and no `revision_id`). The returned `revision_id` is the optimistic-locking witness — pass it back to `update_account_overview` to detect concurrent edits.FaradayFaradayPluginrequiredData & Analytics
- Get account overview revisionget · Retrieve a specific saved revision of the account overview by `revision_id`. Returns the full `content` markdown along with the revision's `created_at`. Use this to inspect history surfaced by `list_account_overview_revisions` — pair it with `update_account_overview` (passing the LIVE revision_id) to roll the overview back to a prior phrasing.FaradayFaradayPluginrequiredData & Analytics
- Get account usageget · Most recent usage-metrics snapshot for the account named by `account_id`, sourced from the latest 'metrics_dashboard' usage event. Per-metric `limit` is intentionally null here — contractual limits live at the parent and are only emitted by get_account_usage_all. Use this for a quick 'how much has been consumed this period' read.FaradayFaradayPluginrequiredData & Analytics
- Get account usage (all subaccounts)get · Usage-metrics snapshot rolled up across the account named by `account_id` and every direct subaccount. Per-metric values are summed; contractual limits come from the parent account only (subaccounts do NOT raise the limit). Use this when checking whether a customer is approaching their plan ceiling.FaradayFaradayPluginrequiredData & Analytics
- Get atlasget · Retrieve a single Atlas by ID, including its `output_to_locations` column mapping, the columns detected in the source data, connection options (with secrets concealed), and the row/locatable counts from its most recent build. `counts.rows` is how many source rows were read and `counts.locatable` how many produced a location — a gap between them means rows could not be placed. Use `get_locations` to read the locations themselves.FaradayFaradayPluginrequiredData & Analytics
- Get attributeget · Get one Attribute definition by ID, including its source Stream, aggregation, value property, interpretation, categories or breaks, status, and effective permissions. The definition can describe a person-level customer fact, behavior, interest, score, or other value. This response returns metadata about the field, not any person's value or the source records used to derive it. A Scope can still include person-level values for delivery through a Target.FaradayFaradayPluginrequiredData & Analytics
- Get cohortget · Retrieve a single Cohort by ID, including its Trait, Attribute, Stream-event, Place, Atlas `location_conditions`, and recency conditions plus the latest `population_count`. Use this to understand exactly who a model or Scope refers to before reusing or changing the Cohort.FaradayFaradayPluginrequiredData & Analytics
- Get cohort membershipget · Get cohort membership counts over time, bucketed by day, week, and month. Useful for sanity-checking that a freshly-edited Cohort behaves as intended (spot step-changes after a config edit), charting how a customer base / churn cohort / lead pool is trending, or confirming a 'recent activity' cohort is the expected size before wiring it into an Outcome's training population.FaradayFaradayPluginrequiredData & Analytics
- Get connectionget · Retrieve a single Connection by ID, including the configured `options` (with secrets like passwords / private keys concealed) and the latest job state. The connection's `directionality` field indicates whether it can be used for ingress, egress, or both.FaradayFaradayPluginrequiredData & Analytics
- Get datasetget · Get one Dataset configuration by ID, including its column-to-Trait mappings, identity fields, place mapping, event Stream outputs, connection options with secrets concealed, and row counts.FaradayFaradayPluginrequiredData & Analytics
- Get dataset ingress logsget · Page through every time Faraday pulled from this Dataset's upstream, with row counts, byte counts, durations, and any errors. Useful for debugging 'why didn't my new rows show up?', charting ingestion volume over time, or spotting a sudden cliff that points at an upstream issue. Pagination is `limit` (capped at 100) + `offset`; `total_count` is included in the response envelope.FaradayFaradayPluginrequiredData & Analytics
- Get locationsget · Page through the locations an Atlas build produced — each with its geometry, its `reference_key`, and the properties its Atlas defines. Pass `atlas_id` to read one Atlas's locations, or omit it to read every location in the account. Use this to confirm a build placed the locations you expected, to look up the reference keys to filter on downstream, or to see which rows failed to geocode (they are absent — compare against the Atlas's `counts`). Pagination is `limit` (capped at 100) + `offset`; `total_count` is included in the response envelope.FaradayFaradayPluginrequiredData & Analytics
- Get market opportunity analysisget · Retrieve one Market Opportunity Analysis by ID, including its Outcome, Scope, optional Persona, job state, overall opportunity summary, and Google Sheets or Slides report URLs once ready. Use the completed report artifacts to inspect market size and location in detail.FaradayFaradayPluginrequiredData & Analytics
- Get migrationget · Retrieve one migration by ID, including the linked FIG v1 and FIG v2 accounts, dataset and target pairs, Lookup API pull counts, approval time, finish time, and job status. Read `account_tree_relationship` before concluding anything about the account hierarchy: when it is `siblings`, the move leaves every parent alone, so a finished migration is expected to leave the FIG v2 account under the same parent it always had, next to the now-suspended FIG v1 account. Only a FIG v2 account created underneath its FIG v1 account changes parent.FaradayFaradayPluginrequiredData & Analytics
- Get outcomeget · Retrieve one Outcome by ID, including its attainment, eligibility, and optional attrition Cohort references, predictor and bias settings, preview and build status, summary performance values, and report URL when available. Use `get_outcome_analysis` for feature importance and full validation metrics.FaradayFaradayPluginrequiredData & Analytics
- Get outcome analysisget · Retrieve a trained Outcome's structured analysis: feature importance and direction, lift curves and tables, ROC curve and AUC, metrics tables, modeling strategies, available tenure splits, and bias measurements. Use this to answer whether the model performs well, which inputs drive it, and how much lift its highest-ranked people provide. Use `get_outcome_report` when a ready-to-read HTML report is wanted instead of structured data.FaradayFaradayPluginrequiredData & Analytics
- Get outcome reportget · Get a 1-hour signed URL pointing at the Outcome's HTML report — the standalone page Faraday generates with the model's marketing-grade summary, feature importances, and validation plots. Returns `{ url, expires_at, filename }`. MCP tools can't stream HTML, so fetch the URL separately when the body is needed.FaradayFaradayPluginrequiredData & Analytics
- Get persona setget · Retrieve a single Persona Set by ID, with each persona's id/name and the source Cohort (as an ID reference).FaradayFaradayPluginrequiredData & Analytics
- Get persona set dimensionsget · For every trait, the distribution per persona (over- and under-indexed values, summary stats). Use this to answer 'what makes each persona different?' and to drive a renaming pass that gives each cluster a real name ('the suburban repeat-buyer', 'the price-sensitive lapser', etc.) via `update_persona`. Same data the Faraday UI renders on the persona-set dimensions page.FaradayFaradayPluginrequiredData & Analytics
- Get placeget · Retrieve a single Place by ID with its full resolved geometry. Use this to verify a store footprint, service area, territory, or drive-time boundary before using it in a Cohort or changing the source locations.FaradayFaradayPluginrequiredData & Analytics
- Get recommenderget · Retrieve one Recommender by ID, including its interaction Stream, item property, predictor settings, preview state, report URL, and latest build metadata. Use this to confirm what behavior and item the model learns from before reusing or changing it.FaradayFaradayPluginrequiredData & Analytics
- Get recommender analysisget · Retrieve a Recommender's cross-validation analysis: feature importance plus top-N accuracy, average true-item rank, item distribution, ROC AUC, and ROC curve, with available splits for new or repeat and recognized or unrecognized people. Use this to judge model quality and choose a useful recommendation count before attaching the Recommender to a Scope.FaradayFaradayPluginrequiredData & Analytics
- Get scopeget · Get one Scope's population and person-level payload configuration, including any Atlas `payload.location` proximity settings, which attach either each person's nearest matching location or every matching location. The response contains configuration, status, columns, and aggregate counts, not person rows or values. Attached Targets can send those rows and values to external systems.FaradayFaradayPluginrequiredData & Analytics
- Get scope analysisget · Get score distributions for each Outcome and Recommender in a Scope, comparing the Scope population with each model's eligible population. Use this to see whether the selected population is concentrated in higher or lower score bands and to choose or review Target score thresholds; read the Scope record itself for population counts and output columns.FaradayFaradayPluginrequiredData & Analytics
- Get scope efficacyget · Get monthly observed attainment for eligible people in each date-based Outcome attached to a Scope, limited to the latest 12 months. Use this after deployment to compare prior predictions with later real outcomes. The report needs an active source Connection, is available only for Outcomes with date-based eligible and attainment Cohorts, starts in the month after Scope creation, and rebuilds monthly; it does not report Persona Set or Recommender efficacy.FaradayFaradayPluginrequiredData & Analytics
- Get streamget · Retrieve one behavioral or assertion Stream by ID or event-type name, including its property metadata. Use this to confirm the event name and available properties before writing a Stream-based Cohort condition, Attribute, or Recommender. The Stream's name appears as `type` in its record, such as `transactions`.FaradayFaradayPluginrequiredData & Analytics
- Get stream analysisget · Get a time-series of event counts for a Stream. Useful for confirming a Dataset is actually emitting events (sanity-check after wiring up new ingress), spotting sudden cliffs that point at an upstream issue, or right-sizing a behavioral Cohort whose `time_window` depends on event recency.FaradayFaradayPluginrequiredData & Analytics
- Get targetget · Get one Target configuration by ID, including its Scope and Connection references, connector options with secrets concealed, representation, filters, limits, status, last successful output time, row count, and final columns. The response does not contain delivered person rows, and Hosted CSV files cannot be downloaded through this MCP.FaradayFaradayPluginrequiredData & Analytics
- Get target analysisget · Get the Target population's distributions for the Traits, Attributes, postcodes, and states selected in its `analysis_config`. Use this to explain who is in the output and check its demographic or geographic composition. Read `get_target` for build status, last output time, record count, and final columns; this analysis does not report delivery success or model lift.FaradayFaradayPluginrequiredData & Analytics
- Get target analysis reportget · Get a 1-hour signed URL pointing at the Target's analysis report (PDF). Returns `{ url, expires_at, filename }`. Fetch the URL separately when the bytes are needed.FaradayFaradayPluginrequiredData & Analytics
- Get traitget · Get one per-person field definition by ID, including its name, description, type, source, coverage, and the Datasets that populate it when it comes from the account's own data. This response returns metadata about the field, not any person's value. A Scope can still include person-level values for delivery through a Target.FaradayFaradayPluginrequiredData & Analytics
- Get trait dimensionsget · For a categorical Trait, the distribution of values across the US population (e.g. `gender`: { female: 0.51, male: 0.48, … }). Useful before relying on a Trait in a Cohort predicate (so the value enum is known) or for sanity-checking representativeness when explaining a model to a client. Numeric/boolean Traits typically return an empty distribution. Same data the Faraday UI renders on the dictionary page.FaradayFaradayPluginrequiredData & Analytics
- Get uploadget · Get a 24-hour signed download URL for an uploaded file. Returned as `{ url, expires_at }`. MCP tools can't stream binary file contents, so fetch the URL separately when the bytes are needed. Returns a 404 error if the file doesn't exist. This tool is disabled in this MCP client by policy. Ask the user to complete this action in Faraday Enterprise at https://app.faraday.ai.FaradayFaradayPluginrequiredData & Analytics
- Get usage statsget · Quota-feature usage for the account named by `account_id`: real-time counts (number of users, scopes, datasets, cohorts, outcomes, persona_sets, recommenders, targets, streams, etc.) paired with the plan/subscription limit for each. Same shape as GET /usages in the REST API. Use this to answer 'are we at our quota for X?' — `get_account_usage` is for billing-period totals; this is for live counts.FaradayFaradayPluginrequiredData & Analytics
- Get use caseget · Retrieve a single Use Case by `id`. Returns the full `title`, `preface` (background / problem / solution markdown blocks), `technical_details` (the machine-readable annex the reviewer and configuration auditor consume), the `draft` flag, the most recent `review` (its `status`, whether the use case is `adequate`, and its findings), and the live `resources` list — every Faraday resource (cohort, outcome, target, scope, recommender, etc.) that has been linked via `link_resource_to_use_case`. (`guide` is deprecated and no longer maintained.) The `revision_id` is the optimistic-locking witness for `update_use_case`.FaradayFaradayPluginrequiredData & Analytics
- Get use case revisionget · Retrieve a specific saved revision of a use case by `revision_id`. Returns the full `title`, `preface`, `technical_details`, and `draft` flag for that revision (`guide` is deprecated and no longer maintained). The `resources` list is intentionally OMITTED on revision reads — resource links are a live property of the use case as a whole, not of any individual revision. Pair with `update_use_case` (passing the LIVE revision_id) to roll back.FaradayFaradayPluginrequiredData & Analytics
- Get webhook endpointget · Get one webhook endpoint's destination URL, status, and lifecycle event subscriptions. The response omits the signing secret, and no MCP read tool can retrieve it after creation.FaradayFaradayPluginrequiredData & Analytics
- Identify the current callerwhoami · Diagnostic: report which Faraday identity the current access token resolves to, and list the names of every tool this MCP exposes. A user identity carries no account — use `list_accessible_accounts` for the account UUIDs your tool calls can act on. Read-only.FaradayFaradayPluginrequiredData & Analytics
- Link resource to use caselink · Link an existing supported resource to the use case it helps implement, so the account documents why that Cohort, model, Scope, Target, Dataset, or other resource exists. The tool validates that both records belong to the account. The link appears in the use case's live `resources` list and is not part of revision history. Linking the same use case, resource type, and resource ID again does not create a duplicate.FaradayFaradayPluginrequiredData & Analytics
- List accessible accountslist · List every Faraday account the caller can act on, with their UUIDs, names, and parent_account_id (if any). Every account-scoped tool call requires an `account_id` from this list, so call this once early in the conversation and keep the UUIDs at hand. For a user, the set matches what the Faraday settings → team UI shows: their current account, accounts they've been explicitly added to, and the direct subaccounts of either. For an M2M client, the set contains its bound account and that account's direct subaccounts. Suspended accounts are filtered out. Read-only.FaradayFaradayPluginrequiredData & Analytics
- List account overview revisionslist · List every saved revision of the account overview, newest first. Returns just `revision_id` and `created_at` per entry — fetch a specific revision's content with `get_account_overview_revision`. Useful for auditing edits or recovering a prior phrasing.FaradayFaradayPluginrequiredData & Analytics
- List accountslist · List the direct subaccounts of the account named by `account_id`. Subaccounts isolate data and configuration for a tenant, sub-brand, region, or business unit. It does not include the parent account itself; use `get_account` for that.FaradayFaradayPluginrequiredData & Analytics
- List atlaseslist · List the collections of geographic locations the account has imported — store footprints, branch networks, dealer lists, service territories. Each Atlas maps a Connection's source columns onto locations, either by address, by latitude/longitude, or by a geometry column. List first before creating a new one: an existing store or branch Atlas is usually the one you want to reuse for spatial Cohort filters, nearest-location Scope payloads, or Market Opportunity Analysis scoping. Secrets in the underlying connection options are concealed.FaradayFaradayPluginrequiredData & Analytics
- List attributeslist · List definitions for Attributes visible to the account. An Attribute projects assertion events into one value per person and records its source Stream, aggregation, value property, null handling, interpretation, and allowed use. Attributes can represent customer facts, behavior, interests, scores, or other person-level data from the account or the built-in consumer catalog. The tool returns field definitions and permissions, not values tied to named people or source records. Other tools can use an Attribute to select people, train models, or include person-level values in a Scope delivered through a Target. On accounts with `identity_graph` set (see `get_account`), this is THE surface for Faraday's built-in consumer data; prefer it over `list_traits` for anything Faraday-provided. On accounts without `identity_graph`, this returns an empty list and the built-in consumer data is exposed as Traits via `list_traits`.FaradayFaradayPluginrequiredData & Analytics
- List cohortslist · List the populations the account already has defined — 'customers', 'churned customers', 'high-value buyers', 'leads in our service area', 'donors who lapsed', etc. A Cohort is a population of people, defined by its trait and/or attribute conditions (e.g. age range, homeownership), stream-event conditions (e.g. 'purchased in the last 90 days'), place conditions, or Atlas `location_conditions` (e.g. 'lives within 10mi of a store'). If you're about to create a new Cohort, listing first lets you reuse an existing one and keeps downstream Outcomes / Persona Sets / Scopes coherent. Each Cohort carries its trait / attribute / stream / place / location conditions, `population_count` (last computed size), and the standard job state.FaradayFaradayPluginrequiredData & Analytics
- List connectionslist · List the external data environments configured on this account. Connections describe how to reach Snowflake, BigQuery, Postgres, S3, GCS, Azure Blob, SaaS systems (HubSpot, Salesforce, Marketo, mParticle, Mailchimp, …), and Faraday-hosted publication types (hosted_csv, lookup_api, merge). If you're about to create a Dataset (ingest), Atlas (locations), or Target (deploy) and want to reuse an existing data environment, call this first. Secrets in `options` are concealed in the response.FaradayFaradayPluginrequiredData & Analytics
- List datasetslist · List the customer, transaction, and event sources the account ingests. Each Dataset maps a table or file from a Connection into identity fields, per-person Traits, event Streams, and optional place data. This response returns configuration, counts, and connection options with secrets concealed.FaradayFaradayPluginrequiredData & Analytics
- List market opportunity analyseslist · List the market opportunity analyses the account already has — reports that answer 'where should we expand?', 'where are our best lookalikes concentrated?', or 'how much likely demand remains in this market?'. Each analysis names the Scope that defines the market, the acquisition Outcome, an optional Persona focus, the latest job state, and report links or summary values once built. Listing first helps reuse an existing study instead of rebuilding the same market question.FaradayFaradayPluginrequiredData & Analytics
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.