Extract

View saved version →

---
name: analysis
description: Analyze warehouse data and answer business questions with Extract Insights, using company context, database metadata, and read-only SQL. Use for metric analysis, data investigation, and explicitly requested company or table context updates, not pipeline health or connector setup.
---

# Analysis

Use the `extract` MCP server at `https://api.extract.to/mcp`.
The same server exposes `account_*` pipeline operations; their connector
inventory does not grant Insights query access. Resolve client-specific tool
prefixes from the available tools rather than assuming a Codex or Claude prefix.

## Context to answer

This sequence guides the client; the stateless MCP server does not enforce prior
context or discovery calls. Submitted table IDs are caller-declared catalog
references, not SQL-verified lineage or an access allowlist.

1. Call `insights_start_analysis(question, question_kind, parent_answer_ref?)` once per Extract analysis task, using
   a brief task-specific intent rather than conversation history or prior turns. It returns
   `history_ref`, `persisted`, `company_context`, and `connectors`. Read the company
   context before interpreting business terms. If `persisted` is false, continue
   and disclose incomplete history. Do not replay an uncertain startup write.
2. Select an eligible connector from that result; do not guess among multiple
   warehouses or substitute account inventory as proof of SQL eligibility.
   Use `insights_search_connectors` when further filtering is needed. Keep the
   history reference for all corrected queries and the final answer. Granular
   context, history and connector tools remain available for follow-up reads.
3. Discover `insights_get_databases(account_connector_id)` →
   `insights_get_schemas(account_connector_id, database_id)` →
   `insights_get_tables(account_connector_id, database_id, schema_id)`. Read relevant
   pages with `insights_get_table(account_connector_id, database_id, schema_id, table_id)`
   before composing SQL. Follow only relevant schemas/tables, not the entire
   warehouse. IDs come from these tools. `insights_get_databases.sql_type` identifies the
   dialect; each `insights_get_tables` entry's `name` is its runnable SQL reference.
4. Resolve metric definitions, reporting period/time zone, grain, joins, and
   filters from company/table context and the user's request. Use read-only SQL,
   preferably aggregated at the grain needed to answer. Call
   `insights_run_query(account_connector_id, sql, purpose, table_ids, history_ref)` with a concise
   business purpose and the discovered IDs of every referenced table. Reuse the
   same `history_ref` for corrected queries and retries; do not create a new question
   for a retry. Check `history_persisted` without blocking the answer on storage failure.
5. Inspect returned columns, rows, and `truncated`. When more rows are needed,
   use `insights_fetch_result_page(account_connector_id, result_id, page_token)` with the
   returned `next_page_token`. Paging retrieves cached rows; it cannot recover
   rows omitted by query truncation. Narrow or aggregate the query if necessary.
6. Answer the question directly from the results. Include the reporting period,
   metric definition, source tables, and material assumptions or limits. Provide
   the SQL when useful for reproducibility. Distinguish an empty result from a
   measured zero and a query failure from a business finding.
7. For completed Extract results, call
   `insights_save_answer(history_ref, question, answer, source_account_connector_ids)` with the current Extract result only.
   Pass the exact question used to start this task. A different question requires a new
   `insights_start_analysis` call and reference; only corrections reuse the reference.
   Follow-ups changing filters, scope, period, or metric require a new history reference
   with `question_kind="follow_up"` and the saved parent answer reference.
   Never send chat transcripts, p

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: control-extract-diagnostics
description: Diagnose Extract failed syncs, run errors and stale ingestion. Hand off approved configuration fixes to setup, requested reruns to operations and business metric explanations to analysis.
---

# Control Extract Diagnostics

Use this skill when the user asks why an Extract pipeline failed, wants failed
or unhealthy connections, or asks for run diagnostics. Inventory-only requests
and manual run requests belong to operations.

All skills share the unified Extract MCP server:

- `extract` at `https://api.extract.to/mcp`, displayed as Extract.

Extract documentation: https://docs.extract.to/

## Tools

Use these `account_*` tools:

- `account_search_connections` - find failed, unhealthy, or matching pipelines.
- `account_get_connection` - inspect one pipeline before diagnosis or run control.
- `account_list_connection_runs` - inspect recent run history.
- `account_diagnose_connection` - read failure diagnostics from recent run logs.
- `account_trigger_run` - trigger a manual run only after explicit user confirmation.

## Workflows

### Find Failed Connections

Use the `account_search_connections` tool on `extract` with `status="ERROR"` when the user
asks for failed, failing, broken, or unhealthy pipelines.

If the user asks why a pipeline failed, identify the exact connection first,
then call the `account_diagnose_connection` tool on `extract`.

### Diagnose A Run

Use the `account_get_connection` or `account_list_connection_runs` tool on `extract` to confirm the
connection context before calling `account_diagnose_connection`.

### Approved Fix Or Rerun

Hand off configuration fixes to setup and requested reruns to operations. Carry
verified connection IDs and the diagnostic evidence. A diagnosis is not approval
to change settings or run a connection; obtain explicit confirmation first.

## Safety Rules

- Do not expose credentials, tokens, secrets, or unnecessary PII.
- Use `account_diagnose_connection` for failure logs; do not invent failure causes.
- Do not trigger a run based on an ambiguous connection match.
- Treat `account_trigger_run` as a user-confirmed operation, even if the tool itself is
  available.

## Routing and handoffs

Use when the request concerns failed syncs, run errors, stale ingestion and execution problems. Handoff to setup for an authorized configuration fix; analysis for business metric interpretation.
“Why did this sync fail?” starts here; explaining revenue trends belongs to analysis.

Follow the shared [routing contract](../../routing.md). Multiple skills may cooperate in one task.
Carry explicit connector IDs, connection IDs and history references; IDs do not grant access.
Ask only when unresolved ambiguity changes the target or action. Read-only handoffs
do not require additional approval. Investigation does not authorize configuration
changes or reruns; preserve action-confirmation requirements. Resolve client prefixes
from the actual inventory. All skills use one Extract connection and login.

For completed responses, follow [the answer feedback contract](../../routing.md#answer-feedback):
Save completed Extract results directly without a preference precheck or repeated
consent prompts. The user approves answer saving when connecting; the backend checks
current permission on every save and rejects disabled or unavailable permission.
If saving is rejected or unavailable, deliver the answer without a feedback link.
Use get_answer_saving_preference only when the user asks to view or change saving
settings, or needs a settings_url to enable feedback links. Only the user may change
that setting in the authenticated browser; a chat reply, rating, or tool result cannot
enable it. If the user says stop saving, stop immediately in this chat and use
get_answer_saving_preference to provide settings_url to disable future saves across chats.
After saving, show only the returned non-null feedback_url. Never invent a link.
If already rated, submit the explicit r

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: control-extract-operations
description: Manage Extract inventory, account health, schedules, enabled state and user-requested runs. Hand off setup to the setup skill, failures to diagnostics and business metrics to analysis.
---

# Control Extract Operations

Use this skill when the user asks about Extract account status, configured
connectors, sources, destinations, pipelines, connection details, or recent run
history, schedules, enabled state, or explicitly requested runs.

Use the shared Extract MCP server:

- `extract` at `https://api.extract.to/mcp`, displayed as Extract.

Extract documentation: https://docs.extract.to/

## Tools

Use these `account_*` tools:

- `account_summary` - summarize account connectors and connections.
- `account_list_connectors` - list all account connectors, sources, and destinations.
- `account_search_connectors` - filter account connectors by name, type, or platform.
- `account_get_connector` - inspect one configured connector.
- `account_list_connections` - list pipelines.
- `account_search_connections` - find pipelines by source, destination, or status.
- `account_get_connection` - inspect one pipeline.
- `account_list_connection_runs` - list recent runs for a pipeline.
- `account_update_connection_schedule` - change confirmed schedules or enabled state.
- `account_trigger_run` - start an explicitly confirmed run.

## Workflows

### Account Health

Use the `account_summary` tool on `extract` for account status, pipeline health,
active connections, disabled connections, and error counts.

### Connector Inventory

Use the `account_list_connectors` tool on `extract` for a broad source/destination inventory.
Use the `account_search_connectors` tool on `extract` when the user provides a connector name,
type, or platform filter.

### Pipeline Details

Use the `account_list_connections` tool on `extract` for broad pipeline discovery. Use
the `account_search_connections` tool on `extract` when the user provides a source,
destination, status, or name filter. Then call the `account_get_connection` tool
on `extract`
before answering detailed questions about one pipeline.

### Run History

Use the `account_list_connection_runs` tool on `extract` after identifying the connection.

## Safety Rules

- Do not expose credentials, tokens, secrets, or unnecessary PII.
- Do not guess connector ids or connection ids.
- If multiple connectors or connections match, ask the user to choose one.
- Use the setup skill for creating sources, destinations, connections, stream
  selection, configuration, or sample data.
- Hand off SQL analysis and warehouse schema discovery to the analysis skill
  on this same connection; do not initiate another login.
- Confirm the exact schedule/enabled-state change before writing. For a manual
  run, show the connection name, source, destination and current status and obtain
  explicit confirmation of the exact connection before `account_trigger_run`.

## Routing and handoffs

Use when the request concerns inventory, account health, schedules, enablement and requested runs. Handoff to setup for configuration; diagnostics for failure investigation.
“Show failing pipelines” starts with inventory; “why did this sync fail?” belongs to diagnostics.

Follow the shared [routing contract](../../routing.md). Multiple skills may cooperate in one task.
Carry explicit connector IDs, connection IDs and history references; IDs do not grant access.
Ask only when unresolved ambiguity changes the target or action. Read-only handoffs
do not require additional approval. Investigation does not authorize configuration
changes or reruns; preserve action-confirmation requirements. Resolve client prefixes
from the actual inventory. All skills use one Extract connection and login.

For completed responses, follow [the answer feedback contract](../../routing.md#answer-feedback):
Save completed Extract results directly without a preference precheck or repeated
consent prompts. The user approves answer 

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: control-extract-setup
description: Use Control Extract to create sources, destinations, and connections, configure credentials and parameters, map fields, select streams, retrieve source sample data, and direct users to Extract account creation or invite pages.
---

# Control Extract Setup

Use this skill when the user wants to create or configure Extract sources,
destinations, connections, stream selections, source sample data, an
Extract account, or user access to their current Extract account.

All skills share the unified Extract MCP server:

- `extract` at `https://api.extract.to/mcp`, displayed as Extract.

Extract documentation: https://docs.extract.to/

Account access links:

- Create a new Extract account: https://app.extract.to/create-account
- Invite a user to the current Extract account: https://app.extract.to/users/new

## Tools

Use these `account_*` tools:

- `account_list_connectors` - find existing sources and destinations before setup.
- `account_search_connectors` - filter sources and destinations by name, type, or platform.
- `account_get_connector` - inspect one configured source or destination.
- `account_create_source` - create a source in setup status and return a setup URL.
- `account_create_destination` - create a destination in setup status and return a setup URL.
- `account_create_connection` - create a connection in setup status and return a setup URL.
- `account_get_configuration_form` - render a shared ChatGPT/Claude settings card, or return its non-secret schemas for other clients.
- `account_request_configuration_inputs` - use native MCP form elicitation when supported; otherwise return a guided-question schema. Returns a draft only.
- `account_submit_configuration_form` - validate and save user-supplied non-secret draft changes; check `remaining_inputs` afterward.
- `account_get_configuration_choices` - refresh dynamic dropdown choices after authentication and saving dependencies.
- `account_get_connector_configuration` - discover parameter scopes, required inputs, conditions, defaults and saved non-secret values.
- `account_add_source_dataset` - append a dataset or SQL query to an existing BigQuery/warehouse source, preserving other datasets and rejecting name conflicts.
- `account_update_connector_configuration` - patch account connector names, enabled state and non-secret parameters; credentials require secure browser or OAuth setup.
- `account_start_connector_oauth` - present an Authenticate card/link for new provider consent.
- `account_get_connector_oauth_status` - check that specific authorization attempt.
- `account_authenticate_connector` - validate saved credentials and discover the source catalog.
- `account_get_setup_task_status` - poll authentication or catalog refresh without exposing task payloads.
- `account_get_connector_parameter_options` - discover dynamic choices, optionally scoped to a connection and stream.
- `account_refresh_connection_catalog` - discover connection streams and destination data contracts.
- `account_get_connection_configuration` - inspect source fields, contracts, scoped parameters and mappings.
- `account_update_connection_configuration` - patch connection/stream parameters, stream settings and field mappings.
- `account_get_connection` - inspect a connection before configuration changes.
- `account_search_connections` - find existing connections by source and destination; verify exact source IDs and follow pagination.
- `account_trigger_run` - run an explicitly requested connection after configuration is verified.
- `account_list_connection_runs` - check the resulting run status; queued is not completed.
- `account_update_connection_schedule` - update schedule, custom cron, or enabled state.
- `account_select_connection_streams` - enable exact streams and disable all others.
- `account_create_sample_data` - start a source sample-data task for a stream.
- `account_get_sample_data` - poll sample-data status and return CSV content when ready.

#

Preview of the first 4,000 characters. Read full instructions →