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

update-syntheia-workspaceupdate · Update properties of a Syntheia workspace. Only provided (non-None) fields are sent in the update payload. Args: workspace_id: The numeric workspace ID to update. name: New display name. active: Set workspace active or inactive. language: Primary language (e.g. "english", "french"). protected: Restrict access to authorized users only. document_limit: Maximum number of documents allowed (None = no limit). Returns: Confirmation with the updated workspace name.SyntheiaSyntheiaPluginrequiredOperations
upload-syntheia-documentupload · Upload and register one attached document in a single tool call. Use this path when the MCP client supplies an attachment as a pre-authorized file reference, as ChatGPT does. The server downloads the attachment, computes its MD5 hash, uploads it to Syntheia storage, and registers it for indexing. Claude clients that expose local file bytes instead should retain the prepare-syntheia-upload -> direct PUT -> register-syntheia-document workflow; do not place file bytes or base64 data in tool arguments. Args: document: The attached file reference supplied by the MCP client. title: Optional workspace display title; defaults to the attachment's filename, or its file ID when no filename is available. Returns: The existing or newly registered document ID.SyntheiaSyntheiaPluginrequiredOperations
Sonraki İlanlarload · Önceki ilan aramasının SONRAKİ sayfasını döner. cursor alanına en son arama sonucunda dönen cursor değerini olduğu gibi gönder. Arama sorgusu, filtreler ve sıralama cursor'ın içinde taşınır; sorguyu tekrar yazmana gerek yok. Kullanıcı 'devamını göster', 'daha fazla ilan' dediğinde bunu kullan.REMAX TurkiyeRE/MAXPluginnoneOperations
Sıralamayı Değiştirsort · Önceki aramanın SONUÇLARINI yeni bir sıralamayla, ilk sayfadan döner. cursor alanına en son sonuçtaki cursor'ı, sort alanına istenen sıralamayı gönder. Arama kriterleri cursor'ın içinde taşındığı için sorgu yeniden yorumlanmaz — kullanıcı 'en ucuzdan sırala', 'en yeniler önce' dediğinde search_properties'i tekrar çağırmak yerine bunu kullan.REMAX TurkiyeRE/MAXPluginnoneOperations
İlan Arasearch · RE/MAX Türkiye'nin aktif satılık/kiralık emlak ilanlarında doğal dilde arama yapar ve ilk sayfayı döner. query alanına kullanıcının aradığı ilanı anlatan tam bir Türkçe cümle gönder; konuşmada netleşen tüm kriterleri (il, ilçe, mahalle, site adı, kategori, oda sayısı, metrekare, fiyat aralığı gibi) aynı cümlede topla. Örnek: 'Kadıköy Fikirtepe'de 10 milyon TL'ye kadar 3+1 satılık daire'. ÖNEMLİ: Her çağrı tek başına okunur, önceki aramayı hatırlamaz. Kullanıcı bir kriteri değiştirdiğinde yalnızca değişikliği değil, hâlâ geçerli olan diğer tüm kriterleri de aynı cümlede TEKRAR yaz; sadece kullanıcının açıkça vazgeçtiği kriteri çıkar. Örnek: 'Kadıköy'de 3+1 kiralık daire' aramasından sonra kullanıcı 'vazgeçtim satılık olsun' derse gönderilecek cümle 'Kadıköy'de 3+1 satılık daire' olmalıdır — 'satılık daire' göndermek Kadıköy ve 3+1 kriterlerini sessizce düşürür ve kullanıcıya alakasız ilanlar döner. Sonraki sayfalar için bu tool'u tekrar çağırma, dönen cursor ile load_more kullan.REMAX TurkiyeRE/MAXPluginnoneOperations
İlan Detayıget · Tek bir ilanın tam kaydını döner: ilan açıklaması, kategoriye özel tüm özellikler ve fotoğraf listesi. code alanına ilanın portföy numarasını (örn. P50283306) ya da remax.com.tr portföy linkini gönder. Kullanıcı listedeki bir ilanın detayını, açıklamasını veya fotoğraflarını sorduğunda kullan.REMAX TurkiyeRE/MAXPluginnoneOperations
Add a product to the Fotoluce cartadd · Add a current Fotoluce item_id to the linked customer’s shared cart. Use the generation from get_cart and a unique idempotency_key; prices, limits, availability, and coupons are revalidated by Fotoluce.FotoluceFotolucePluginoptionalCommerce
Clear the Fotoluce cartclear · Remove every product from the linked customer’s Fotoluce cart. Use the current generation and a unique idempotency_key.FotoluceFotolucePluginoptionalCommerce
Continue to Fotoluce checkoutcreate · Create a short-lived, customer-bound Fotoluce checkout link for the current shared cart. The customer confirms delivery, final price, and payment on Fotoluce; this tool does not place or pay an order.FotoluceFotolucePluginoptionalCommerce
Get Fotoluce cartget · Read the linked customer’s durable Fotoluce cart, including current prices, automatic discounts, availability warnings, and the generation required for safe updates.FotoluceFotolucePluginoptionalCommerce
Get Fotoluce store informationget · Return Fotoluce-owned store, pickup, delivery, return, support, and policy information. Delivery timing and final charges are confirmed only in the Fotoluce checkout.FotoluceFotolucePluginoptionalCommerce
Get a Fotoluce orderget · Get one order belonging to the linked Fotoluce customer, including delivery or pickup details, line items, totals, payment options, and tracking. It cannot access another customer’s order.FotoluceFotolucePluginoptionalCommerce
Get a Fotoluce productget · Resolve one stable Fotoluce item_id from the official product feed. Returns current catalogue facts, published attributes, active promotion descriptions, and curated included-in-box or often-bought-together relationships, or an explicit unavailable/not_found status. Attributes such as lens mount and explicit brand/model compatibility can support kit selection, but a relationship alone must not be presented as technical compatibility.FotoluceFotolucePluginoptionalCommerce
Get linked Fotoluce accountget · Return the identity and account links for the Fotoluce customer who explicitly linked this conversation.FotoluceFotolucePluginoptionalCommerce
List Fotoluce orderslist · List the linked customer’s Fotoluce orders with the status, totals, products, discounts, payment state, fulfillment state, and tracking shown in the account order page.FotoluceFotolucePluginoptionalCommerce
Remove a Fotoluce cart itemremove · Remove one line from the linked customer’s cart. Use line_id and generation from get_cart plus a unique idempotency_key.FotoluceFotolucePluginoptionalCommerce
Search Fotoluce productssearch · Search current, published standard products sold by Fotoluce. Pass concise product names or model identifiers as query (for example A6400), not the complete user sentence. Prices are integer minor units; current_price is authoritative for the observed response. Each result includes its active promotions and their official descriptions when available; use them for related-purchase questions without inferring missing eligibility.FotoluceFotolucePluginoptionalCommerce
Update a Fotoluce cart quantityupdate · Set the quantity of one current cart line. Use line_id and generation from get_cart plus a unique idempotency_key.FotoluceFotolucePluginoptionalCommerce
Check Simmie connectionping · Liveness and wiring check. Call this once when configuring a new MCP client to confirm Simmie is reachable and the credentials are valid. Returns a static payload; takes no arguments. Use this only for setup or troubleshooting — it has no product effect.SimmieSimmiePluginrequiredSales & CRM
Create a roleplay simulationcreate · Create a complete Simmie roleplay simulation from a plain-English brief and return a shareable practice link. This generates a training module, a roleplay persona, and an evaluation rubric, saves them together, and binds them — all in one call. Use this whenever the user wants to 'make a roleplay', 'build a practice scenario', or 'create a simulation' for their team. Returns the module/persona/rubric ids and a practice_url to share. Always generates a NEW persona — it cannot be pointed at an existing one, so check list_personalities first if the user may already have a suitable persona and wants to avoid a near-duplicate. Ownership follows the signed-in account and is not selectable: team accounts create simulations shared with the whole organisation, individual accounts create private ones.SimmieSimmiePluginrequiredSales & CRM
List existing personaslist · List the roleplay personalities (personas) the current user/org already has in Simmie. Call this before creating a simulation so you can tell the user what they already own and let them decide, or to show them their library. You cannot reuse one — create_simulation always generates a fresh persona. Read-only; takes no arguments. Returns id, name, a short summary, profession, gender, difficulty, and owner scope for each.SimmieSimmiePluginrequiredSales & CRM
Gomoku 오목 대국 시작start · [Gomoku — Play Five in a Row against AI] Opens a real, playable Gomoku board so the user can play a full game against the AI. Also known as: 오목, omok, renju, 렌주, gobang, five in a row, connect five, 五目並べ, gomoku narabe, 五子棋, wuziqi, caro, piskvorky. Call this tool whenever the user wants to play Gomoku / Omok / Renju / five-in-a-row, asks for a Gomoku board or a five-in-a-row game, or says something like "오목 두자", "let's play gomoku", "五目並べやろう", "下五子棋", "chơi caro". Do not describe the rules first and do not play for the user — just open the board. Choosing options: - boardSize: 15 is the default and is the official tournament board for both Gomoku and Renju. Use 19 only if the user asks to play on a Go board, 13 for a deliberately quick game. - ruleset: standard by default (exactly five wins; six in a row does not). Pick renju when the user asks for professional / tournament / Renju rules with forbidden moves. Pick freestyle when the user wants casual rules where six or more also wins. - opening: free by default. Use pro or longpro only if the user asks to balance black's first-move advantage. - playerColor: black unless the user asks to play white. Black moves first. - level: normal by default. easy for beginners or children, hard if the user wants a real fight. - language: match the user's language. After calling, reply in one or two short lines. Do not comment on the position, do not suggest moves, and do not narrate the game — the widget drives everything until the game ends.GomokuDoctor FortunePluginnoneConsumer & Lifestyle
Gomoku 착수play · 위젯 전용. 사용자의 착수·기권·무르기를 반영하고 AI 응수까지 계산한다. 모델이 직접 부르지 않는다.GomokuDoctor FortunePluginnoneConsumer & Lifestyle
Archive resourcearchive · Archive a supported resource to stop future updates without deleting its configuration. If live downstream dependencies block the change, inspect the dependency graph and acknowledge the exact resources with `cascade_to`, or acknowledge all of them with `cascade_to_all`; archive cascades downstream. A migration that observes a resource does not block archive and is not cascaded. Do not assume archiving cancels work already in flight: inspect a Target's status before using this to pause external delivery, and treat an active run as potentially completing. Resources that have never built may not yet support archiving. Built-in Traits are read-only. Use deletion only when the configuration should be removed.FaradayFaradayPluginrequiredData & Analytics
Archive use casearchive · Archive a use case. Sets `archived_at` to the current time. Archived use cases still appear in `list_use_cases` and `get_use_case` (so audit / recovery work), but the dashboard hides them by default. Outside the revision stream — does not bump `revision_id`. Reversible with `unarchive_use_case`.FaradayFaradayPluginrequiredData & Analytics
Create accountcreate · Create a direct subaccount when one customer needs separate data, users, and configuration for a brand, region, business unit, or other access boundary while billing remains with the parent. Each subaccount gets its own Connections, Datasets, Cohorts, models, Scopes, and Targets. Only a top-level account can create one, and subaccounts cannot nest further. The new account inherits the parent plan and eligible grants. This provisions a billable account, and its name appears in customer-facing records.FaradayFaradayPluginrequiredData & Analytics
Create atlascreate · Create an Atlas that imports geographic locations — stores, branches, dealers, or service points — from a Connection so Cohorts can filter people by proximity, Scopes can attach the nearest location to each person, and Market Opportunity Analyses can scope to a footprint. Required: `name`, `options` with `type` (and `connection_id` unless the account's hosted CSV connection should be provisioned), and `output_to_locations`. `output_to_locations` must place each location by exactly one of three column groups: address columns (`house_number_and_street`, `city`, `state`, `postcode`), a `latitude`/`longitude` pair, or a single `geometry` column — mixing them is rejected. Set `reference_key` to give locations stable identifiers so downstream Cohorts, Scopes, and Market Opportunity Analyses can filter to specific ones, and `properties` to carry extra per-location values to filter on. Addresses are geocoded during the build. Hosted CSV data must already be uploaded to the directory named in `options`. Creation queues asynchronous ingestion; check the job state and `counts` before building downstream resources.FaradayFaradayPluginrequiredData & Analytics
Create attributecreate · Create an Attribute that projects assertion events into one value per person, such as current loyalty tier, latest product category, or total activity. Cohorts can select people by the value, models can use it, and Scopes can deliver it through Targets. This tool defines the projection but does not upload or return source records or person-level values. Required: `name`, `literate`, `description`, `category`, `tier`, `feature_store_id`, `stream_name`, and `value_property_name`. The feature store and Stream must already exist in the account.FaradayFaradayPluginrequiredData & Analytics
Create cohortcreate · Create a Cohort, the reusable population definition for goals such as customers who churned, high-value buyers, unconverted leads, lapsed donors, recent purchasers, or people near stores or service points. Outcomes use Cohorts as target and eligibility populations, Persona Sets use them as segmentation sources, and Scopes use them as delivery populations or exclusions. Required: `name`. Membership may use Trait, Attribute, Stream-event, Place, Atlas `location_conditions`, and recency conditions; inspect the relevant list tools first to find valid inputs, and include `stream_name` with Stream conditions. Prefer `location_conditions` for store/branch footprints, naming the atlases under `locations`; a Cohort may not set both `location_conditions` and `place_conditions`. Required conditions combine with AND, while optional conditions form an OR group. Creation starts asynchronous population evaluation.FaradayFaradayPluginrequiredData & Analytics
Create connectioncreate · Create a Connection so the account can read customer data from, publish results to, or import locations from an external warehouse, cloud store, or SaaS system. A Connection is the shared access and credential layer: create a Dataset against it for ingestion, an Atlas against it for locations, or a Target against it for delivery. `options.type` selects connectors such as Snowflake, ClickHouse, BigQuery, Postgres, S3, GCS, Azure Blob, HubSpot, Salesforce, Marketo, or mParticle and determines the credential fields. Confirm that the connector supports the intended ingress or egress direction before creating it. `classic` and platform-managed types such as `hosted_csv`, `lookup_api`, and `merge` cannot be created here. Snowflake creation generates an RSA keypair and returns the public key that must be installed in Snowflake. ClickHouse creation generates an Ed25519 keypair and returns the OpenSSH public key that must be installed on the ClickHouse user. BigQuery, GCS, and S3 creation assigns a unique Faraday service account or IAM role (`gcp_service_account_email` or `aws_iam_role_arn`); grant that account or role access, then force-update. 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
Create datasetcreate · Create a Dataset that tells the account how to import one customer, order, lead, donation, attendance, or event source from a Connection. It resolves rows into people through identity fields, maps source columns into per-person Traits, and emits event rows into Streams for audiences and models. Required: `name`, matching `options.type` and `connection_id`, and `identity_sets`. Creation queues ingestion of the source data.FaradayFaradayPluginrequiredData & Analytics
Create market opportunity analysiscreate · Create a Market Opportunity Analysis to size and map where likely customers are concentrated for questions such as where to expand, which regions have the most headroom, or where strong lookalikes live. It turns an acquisition Outcome over a Scope's market population into a geographic opportunity report; use a Persona when the question concerns one customer segment. Required: `name`, `scope_id`, and `outcome_id`; the Outcome must already be in the Scope payload. Optional `persona_set_id` and `persona_id` narrow the analysis, and the Persona Set must also be in the Scope payload. Optional `locations` with `atlas_ids` scopes the report to specific Atlas footprints. The Scope should cover the full market being measured and should not exclude existing customers, since they provide evidence of demand. Creation starts an asynchronous report build and may require an enabled plan feature.FaradayFaradayPluginrequiredData & Analytics
Create migrationcreate · Create a FIG v1-to-v2 migration owned by the current FIG v2 account. Required: `type: fig_v1_to_fig_v2`, `fig_v1_account.id`, `datasets`, and `targets` (either array may be empty). The creating user must have access to both accounts, and paired datasets/targets must belong to the stated accounts. The two accounts must also be related in the account tree, sharing a parent or one being the parent of the other, which guards against naming the wrong account: account names are not unique. Name the account whose work was rebuilt, never a parent account that merely contains it. A FIG v2 account that is the parent of the FIG v1 account is only accepted when it holds no other accounts, because migrating would otherwise show the FIG v1 members every other account under that parent. Approving the migration suspends the FIG v1 account, so naming a parent suspends the account that holds the contract and the usage roll-up for everything beneath it. The relationship also decides what the move does to the hierarchy: siblings both keep their parent, while a FIG v2 account created underneath its FIG v1 account moves up into its place and adopts its other subaccounts. Accounts already paired by a migration cannot be paired again unless that migration was rolled back.FaradayFaradayPluginrequiredData & Analytics
Create outcomecreate · Create a propensity Outcome for questions such as who will churn, convert, buy again, donate, attend, upgrade, respond, or become high value. The platform learns from the account's person attributes and behavior, then scores people by how likely they are to attain the behavior represented by a Cohort. Required: `name` and `attainment_cohort_id`, the Cohort of people who attained it. Optional: `eligible_cohort_id` limits who can be scored, while `attrition_cohort_id` supplies clear counterexamples. After the model builds, inspect its analysis and add the Outcome to a Scope payload to publish scores for retention, acquisition, lead ranking, or other action. With `preview: true`, the configuration is saved but the model does not build; otherwise creation starts an asynchronous build whose progress appears in the returned resource's job state.FaradayFaradayPluginrequiredData & Analytics
Create persona setcreate · Create a Persona Set to discover distinct, data-driven groups within a customer, donor, lead, fan, or other Cohort. The platform clusters people by shared attributes, which answers questions such as 'what kinds of buyers do we have?' without requiring segment rules in advance. Required: `name` and `cohort_id`. Leave `number_of_clusters` unset to choose the cluster count automatically; set it only when the use case requires an exact count. `preview: true` saves the configuration without building it. After the asynchronous build finishes, use `get_persona_set_dimensions` to understand each group, rename its Personas with `update_persona`, and add the Persona Set to a Scope payload when each person should receive a segment assignment.FaradayFaradayPluginrequiredData & Analytics
Create placecreate · Create a reusable Place for geographic questions such as people near stores, households inside a service area, or leads in a sales territory. Use the Place in a Cohort's place conditions to include or exclude people by location; that Cohort can then drive modeling, market analysis, or delivery. Required: `name` and exactly one location source: `geojson` or `addresses`. Address inputs are resolved asynchronously, so poll the Place's `status` before using it. The schema defines the accepted GeoJSON shapes and address fields.FaradayFaradayPluginrequiredData & Analytics
Create recommendercreate · Create a Recommender for per-person next-best products, content, offers, locations, courses, categories, or upgrades. It learns from one interaction Stream, such as transactions, views, plays, or visits, and the chosen Stream property names the item being recommended. Required: `name`, `stream_name`, and `stream_property_name`; inspect the Stream first to confirm that it has enough recent events and the item property is populated. After the model builds, inspect its analysis and add it to a Scope payload to publish ranked recommendations. `preview: true` saves the configuration without building it. This feature is experimental and may require plan access.FaradayFaradayPluginrequiredData & Analytics
Create scopecreate · Create a Scope that selects people and produces person-level fields for delivery. Its population combines Cohorts and exclusions; its payload can include identity fields, predictions, Persona membership, recommendations, Traits, Attributes, Cohort membership, and proximity to Atlas locations via `payload.location`. A Scope computes this data but does not send it until a Target uses it. Required: `name`, `population`, `payload`, and `preview`. An empty `population.cohort_ids` can select the entire available US population. Start in preview and confirm the population and fields before turning off preview mode.FaradayFaradayPluginrequiredData & Analytics
Create streamcreate · Find or create a Stream, the typed event channel for a kind of customer behavior such as transactions, signups, cancellations, page views, donations, clicks, attendance, or support events. Datasets emit events into Streams; behavioral Cohorts query them, Outcomes learn from them, and Recommenders use them as interaction histories. Names are lowercase identifiers that start with a letter and may contain digits or underscores. If the name already exists, the existing Stream is returned unchanged. Dataset `output_to_streams` mappings usually create Streams automatically; invoke this tool only when the Stream must exist before its Dataset mapping is added.FaradayFaradayPluginrequiredData & Analytics
Create targetcreate · Create a Target that sends a Scope's person-level population and payload to a destination. The payload can include identity fields, predictions, Persona membership, recommendations, Traits, Attributes, and Cohort membership. Destinations include ad platforms, email and customer systems, warehouses, files, the Lookup API, and webhooks. Without a Target, a Scope computes context but does not send it anywhere. Required: `name`, `scope_id`, connector-specific `options`, and `representation`; destinations backed by a Connection also require `connection_id`. Creation may send customer data outside Faraday, so confirm the destination, population, payload, representation, filters, and limits with the user before calling this tool.FaradayFaradayPluginrequiredData & Analytics
Create traitcreate · Find or create a field for a stable per-person value from the account's own data, such as loyalty tier, lifetime value, preferred category, internal score, or customer status. A Dataset populates it through `output_to_traits`; Cohorts can then select people by the value, models can use it, and Scopes can deliver it through Targets. This tool defines the field but does not upload or return person-level values. `name` must be lowercase snake case and unique within the account. Set `statistical_type` to match the field's meaning.FaradayFaradayPluginrequiredData & Analytics
Create uploadcreate · Upload a UTF-8 flat file of customer, order, lead, donor, or event data to the account's Hosted CSV storage. The `content` argument is the raw file body. Use it only when the user asks to add the file to the account. A file with the same directory and filename is replaced, and matching Hosted CSV Datasets are queued to ingest it. This inline tool is for megabyte-scale files; use an S3 or GCS Connection for larger or recurring files. 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
Create use casecreate · Create a use case, the account's durable record of one customer problem and how the configured resources solve it. Use this for goals such as churn prevention, lead scoring, donor reactivation, audience delivery, or market expansion so later operators and agents can recover the intent behind the resource graph. Required: `title`. Optional `preface` fields record the background, problem, and solution; optional `technical_details` markdown records the machine-readable annex the reviewer and configuration auditor consume, and `draft` marks the use case a work in progress. After creation, link each Cohort, Outcome, Scope, Target, Recommender, or other resource that implements the use case with `link_resource_to_use_case`.FaradayFaradayPluginrequiredData & Analytics
Create webhook endpointcreate · Create an HTTPS webhook endpoint so another system can react when asynchronous resource work fails or finishes with new output, such as refreshing a dashboard after Target delivery, starting work after Dataset ingestion, or alerting on a model error. Subscribe with `resource.errored` and/or `resource.ready_with_update`. The response returns the signing secret exactly once; store it before discarding the response so the receiver can verify later deliveries. If it is lost, delete and recreate the endpoint.FaradayFaradayPluginrequiredData & Analytics
Delete migrationdelete · Delete an unapproved migration owned by the current FIG v2 account. Approved migrations cannot be deleted, including ones support has rolled back, though a rolled-back migration stops blocking a new migration for the same accounts.FaradayFaradayPluginrequiredData & Analytics
Delete resourcedelete · Delete a supported resource. By default the resource is soft-deleted and hidden while stored references remain; `hard_delete: true` removes it outright. Deletion is refused while blocking downstream dependencies remain, so inspect the dependency graph first. Archive the resource instead when a reversible pause is required. Accounts, Attributes, uploads, webhook endpoints, and use cases use other lifecycle tools.FaradayFaradayPluginrequiredData & Analytics
Delete uploaddelete · Permanently delete one hosted CSV file. The call returns 404 when the file does not exist. Every Dataset for the same directory is queued to remove rows that came from the deleted file, and every Atlas for the same directory is rebuilt without it, which can change downstream populations and deliveries.FaradayFaradayPluginrequiredData & Analytics
Delete webhook endpointdelete · Permanently delete a webhook endpoint. Delivery stops and the signing secret cannot be recovered. Disable the endpoint instead when a reversible pause is required.FaradayFaradayPluginrequiredData & Analytics
Force update resourceforce · Queue an immediate rebuild when fresh work is needed before the normal schedule, such as pulling new source rows, re-evaluating a Cohort, retraining an Outcome, recomputing a Scope, redelivering a Target, or refreshing Migration Lookup API metrics. The resource type determines the work: a Connection is re-read, a Dataset is ingested, an Atlas is rebuilt, a Cohort is evaluated, a model or Scope is rebuilt, a Target is published, and a Migration refreshes metrics (and performs the account move when already approved). The call returns after queuing; inspect the resource job state for completion. Repeated calls made before processing starts may collapse into one run. Confirm the intent before forcing a Target because it sends data to the external destination immediately.FaradayFaradayPluginrequiredData & Analytics
Get accountget · Get the account named by `account_id`, including its name, parent account, contract renewal date and monthly cost, job status, and identity-graph configuration.FaradayFaradayPluginrequiredData & Analytics

Tool Explorer FAQ

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.