delete-agents
ChatGPTDelete an AI agent for the team (soft delete). Deletion is blocked while the agent has active conversations (processing, retrying, cancelling, or awaiting action) — wait for them to finish or cancel them first. Use action=delete with an agent_ulid. Use list-agents with action=list to find ULIDs. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: agent schedules, agent triggers, conversations. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-ai-visibility
ChatGPTPermanently delete an AI visibility monitor, its prompts, and all captured answers. The monitor's data source is removed from the team, so widgets built on it stop loading. Use action=delete_monitor with the monitor_id from list-ai-visibility. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, reports. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-automations
ChatGPTRemove scheduled report delivery configurations. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: scheduled report deliveries. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-blends
ChatGPTDelete data blends. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, reports, filters, goals. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-conversations
ChatGPTArchive one of your conversations. An archived conversation stops all its work, including the schedules that wake it, and is deleted for good after 30 days unless the user restores it in the Whatagraph app. Only type=user (chat) conversations can be archived — inter-agent and builder conversations are managed by their agent lifecycle and are not deletable here. It is blocked while a conversation is still active (processing, retrying, cancelling, or awaiting action) — cancel it first. Use action=delete with a type and conversation_id. Destructive actions. Every action of this tool: permanently deletes data. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-custom-dimensions
ChatGPTPermanently delete one or more custom dimensions and all their related mappings, tags, and fields. A dimension still used by widgets or filters is blocked (unless force=true) and the references are reported, because deletion is a hard delete that cannot be undone. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, filters, reports, blends. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-custom-metrics
ChatGPTPermanently delete one or more custom metrics and all their related field mappings. A metric still used by widgets or filters is blocked (unless force=true) and the references are reported, because deletion is a hard delete that cannot be undone. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, filters, reports. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-destinations
ChatGPTDelete data transfers. This removes the ETL transfer configuration and stops data syncing. Use action to choose the operation: - delete — delete a transfer. Requires confirmation. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: source groups, widgets. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-dynamic-integrations
ChatGPTDelete a dynamic integration that has never been connected. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: integration_definitions, integration_keys. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-filters
ChatGPTDelete a filter by ID. This removes the filter (soft delete). Use action to choose the operation: - delete — remove a filter (soft delete) Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, blends, overviews. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-goals
ChatGPTDelete goals. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: overviews. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-overviews
ChatGPTDelete overviews. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: overview shares. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-reports
ChatGPTDelete reports. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: report tabs, widgets, automations, shares, snapshots. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-sharing
ChatGPTRemove public share links from reports and overviews. Target a report with report_id or an overview with overview_id — one or the other, never both. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: public links already handed out. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-snapshots
ChatGPTDelete report snapshots. Use action to choose the operation: - delete — delete a snapshot Destructive actions. Every action of this tool: permanently deletes data. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-source-groups
ChatGPTDelete source groups. This removes the source group, its configs, sources, and the associated virtual integration source. This action cannot be undone. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, blends, reports, transfers. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-sources
ChatGPTRemove data sources from the team. This disconnects the source and removes its data from reports. Use source_ids to specify which sources to delete. Requires confirmation. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: widgets, blends, reports, goals, source groups. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-spaces
ChatGPTDelete spaces. Cannot delete the "Home" space. If a user says "space", "folder", or "client", they mean a space. Use action=delete with a client_id to soft-delete a space and all its reports. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: reports, overviews, member access. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
delete-templates
ChatGPTDelete report templates. Does NOT delete reports created from the template. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: linked reports. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
export-report
ChatGPTExport all widgets in a report (or a single tab) as CSV in one call. Use this instead of calling list-widgets with action=csv_export once per widget — one export-report call returns every widget's CSV plus metadata (title, source, date range, widget type), grouped by tab. Parameters: - report_id (required) — report to export - tab_id (optional) — limit to a single tab - widget_ids (optional) — limit to specific widgets - from / till (optional, YYYY-MM-DD) — fallback date range for widgets that don't have one configured Comment, calendar, image, and filter control widgets are skipped (no tabular data).
fetch-data
ChatGPTFetch marketing data from a connected source. Returns rows of metric values optionally grouped by dimensions for a date range. Use the list-sources tool first to discover available sources, report types, and field names. Important: if the response indicates data is not yet ready (rate-limited or processing), wait the indicated retry_after seconds and call again with the same parameters.
get-widget-preview-payload
ChatGPTInternal: returns the data payload for a widget preview. Called by the preview app, not by the model. Requires the token from preview-widget.
list-agent-tools
ChatGPTList the canonical catalog of tools that custom agents can be configured with. Call this BEFORE manage-agents (action=create or action=update) to obtain valid tool_name values and pass them verbatim — do not invent or guess names. Optional search filters by tool_name/title/description; category filters by read / write / destructive. Returns each tool's tool_name, title, category, default_permission, a short description, and skills ({core_for, optional_for}) — the skills that need this tool as a core tool vs. use it only in optional sub-workflows.
list-agents
ChatGPTBrowse AI agents for the team. Use action to choose the operation: - list — list all agents for the team (excludes system agents and drafts). When an agent has a pending draft, the listed name/description/model/status reflect the draft, with is_draft=true and has_draft=true. - show — full details for one agent (requires agent_ulid). Returns the pending draft (is_draft/changed_fields) when one exists, else the live agent. tools lists every tool the registry offers, not only the ones this agent holds. Read is_granted before permission: is_granted: false means the agent does not have the tool and will refuse to call it, and permission is only the catalog default it would take if you granted it. Grant one with manage-agents action=update.
list-assets
ChatGPTList the files (assets) available to you. In an agent conversation this is the files owned by this conversation, your agent, or the team; otherwise those owned at the team level, at a space (client) you can access, or on a report under such a space. Returns a manifest with each asset's id, title, type, size, parse status and a short summary — never the full text. Use read-document with an asset id to read a text file's contents. Filter with scope, kind or tag. filter_space_ids / filter_report_ids narrow to assets owned EXACTLY at those space/report nodes. Omit all filters for the full manifest.
list-automations
ChatGPTBrowse scheduled report delivery configurations. If a user says "schedule", "automated report", or "email delivery", they mean automation. Use action to choose the operation: - list — automation schedules for a report - show — full automation details: schedule, timezone, compare type, PDF settings
list-blends
ChatGPTBrowse data blends. Blends combine data from multiple sources into a single virtual data source for cross-channel reporting. Use action to choose the operation: - list — cursor-paginated list of blends with optional search/filter (pass cursor from page.cursor for next page) - show — full blend details with sub-sources, join configuration, and usage stats
list-conversations
ChatGPTBrowse conversations across all three conversation domains. Pass type to choose the domain and action for the operation (valid actions depend on the type): - type=inter_agent — list_roots (top-level conversations), list_children (children of a parent, requires parent_conversation_id), show (transcript, requires conversation_id). - type=user — list (Chat conversations), show (transcript, requires conversation_id). - type=builder — list (Agent Builder conversations, optional filter_context_agent_ulid), show (transcript, requires conversation_id). filter_status and limit (default 50, max 200) apply to the list actions. show returns the conversation header plus a cursor-paginated transcript of the visible user/assistant messages (role, author, content, turn, created_at). Pass include: ["thinking", "tools"] to add thinking rows and tool calls (each paired with its result as one entry). Follow page.cursor to read the rest. On agent-to-agent conversations most activity is tool calls, so the default view can be very short — pass include: ["tools"] to see what the agent actually did. Scope: every conversation on the team, plus your own private ones. Conversations another member marked private are not returned.
list-custom-api-data
ChatGPTRead what a Custom API source already holds. A Custom API source is one you fill in yourself, so this is how you find out what is defined before you write to it with manage-custom-api. Use action to choose the operation: - list_metrics — the metrics defined on the source (external_id, name, type, accumulator) - list_dimensions — the dimensions defined on the source (external_id, name, type) - list_data_points — the stored rows, newest date first. Narrow with from and till Read the metrics and dimensions before defining any, so you update what is there instead of creating a near duplicate.
list-custom-dimensions
ChatGPTBrowse custom dimensions (universal dimensions). These are user-created dimensions that combine or transform data from connected sources. Use action to choose the operation: - list — cursor-paginated team custom dimensions with optional type/search filter (pass cursor from page.cursor for next page) - list_with_premades — cursor-paginated list including premade (system) dimensions alongside team ones - show — full dimension details (metadata, timestamps, creator) - usage — how many widgets/reports use specific dimensions (bulk check)
list-custom-metrics
ChatGPTBrowse custom metrics (universal metrics). These are user-created metrics that combine or transform data from connected sources using formulas or aggregations. Use action to choose the operation: - list — cursor-paginated team custom metrics with optional type/search filter (pass cursor from page.cursor for next page) - list_with_premades — cursor-paginated list including premade (system) metrics alongside team ones - show — full metric details - usage — how many widgets/reports use specific metrics (bulk check)
list-destinations
ChatGPTView data transfers and destination types. Use action to choose the operation: - list — paginated list of transfers with optional filters by name, status, issue, or destination - show — full details for a specific transfer by ID, including its configs - list_jobs — paginated list of ETL jobs for a specific transfer, optionally filtered by config_id and state - list_destination_types — available destination types (BigQuery, Looker Studio, Whatagraph Storage) with their required components and locations
list-dynamic-integrations
ChatGPTList the dynamic integrations this team has built — connectors stored as database rows rather than shipped in code. Each entry reports its status, its live version and its newest version, so a re-draft in progress is visible. Pass channel_id for one integration's full version history, including which version is live and whether the newest draft has been sampled (publishing is gated on that). can_author says whether the calling user may build or change integrations (team admins only). Check it before starting a build, and if it is false, tell the user to ask a team admin.
list-filters
ChatGPTBrowse unified filters. Filters are saved filter configurations that can be applied to data sources and widget configs to narrow down displayed data. Use action to choose the operation: - list — cursor-paginated list of team filters, filterable by name and channel (pass cursor from page.cursor for next page) - show — full filter details with options and values
list-integrations
ChatGPTBrowse available integrations (channels) and connected accounts. If a user says "channel" or "integration", they mean this tool. Use action to choose the operation: - list — all implemented integrations - list_grouped — integrations grouped by category with source counts - list_accounts — connected accounts for a specific integration (requires channel_id) - list_available_sources — available sources for an account (requires account_id)
list-overviews
ChatGPTBrowse overviews (called 'measurements' in the backend) — KPI tracking dashboards that monitor specific metrics over time with visualizations and optional targets. If a user says 'overview', they mean this tool. Use action to choose the operation: - list — cursor-paginated list of team overviews, supports search (pass cursor from page.cursor for next page) - show — full overview details with configs and share settings
list-report-tabs
ChatGPTBrowse tabs (pages) within a report. Each report has one or more tabs, each containing widgets (data visualizations). Called "tabs" in the UI, stored as "report_pages" in the backend. Use the list-reports tool first to find the report, then this tool to explore its tabs. Use action to choose the operation: - list — list all tabs in a report (id, name, position, widget count) - show — full tab details with all widgets and their types
list-reports
ChatGPTBrowse reports within spaces (client folders). Reports contain pages of data visualization widgets. Use the list-spaces tool first to find the right space, then this tool to explore reports inside it. Use action to choose the operation: - list — cursor-paginated list of reports, filterable by name, space, integration, or source (pass cursor from page.cursor for next page) - show — full report details: pages with widgets, date range, share settings - list_sources — list data sources and sample integrations used in a report
list-skills
ChatGPTCALL THIS FIRST — before any other tool — on the first turn of every new conversation, and again when entering a new domain. This discovers the workflow skills for the server: the step-by-step playbooks that carry the correct workflow, field IDs, and gotchas for each Whatagraph task (widgets, blends, filters, reports, automations, sources, and more). Skills are the operating manual — the other tools expose the raw API, and these playbooks tell you how to drive it, so loading the matching one before you build a call is what makes multi-step flows succeed instead of failing on a field name or ID. The index is small, cached, and read-only. Use load-skill to read a skill's full content; skill names follow a predictable whatagraph-<domain> convention, so a known domain can be loaded directly without listing first. Use action to choose the operation: - list — all available skills - search — find skills matching a query (requires query parameter). Supports natural language queries (e.g. "how to create a report") and keyword searches.
list-snapshots
ChatGPTBrowse report snapshots — saved versions of a report's structure. Use action to choose the operation: - list — cursor-paginated snapshots for a report with timestamps and creator (pass cursor from page.cursor for next page)
list-source-groups
ChatGPTBrowse source groups. Source groups combine multiple data sources into a single aggregated source with unified report type configurations. Use action to choose the operation: - list — cursor-paginated list of source groups, supports search (pass cursor from page.cursor for next page) - show — full source group details with sources and configs - source_issues — list sources with disabled ETL configs (sync issues) - list_output_names — list valid output_name values for creating a source group (requires source_ids)
list-sources
ChatGPTBrowse data sources connected to your team. Data sources are specific accounts/properties connected from integrations (e.g. a specific Google Ads account, a specific GA4 property). Use action to choose the operation: - list — list all connected data sources (cursor-paginated, pass cursor from page.cursor for next page) - show — full details for one source (requires source_id) - list_metadata — list metadata for source management; use scope to fetch only what you need (integrations, accounts, spaces, users, tags, categories, or all) - list_report_types — list available report types for a source (requires source_id) - list_dimensions_and_metrics — list available dimensions and metrics (cursor-paginated, requires source_id, optionally report_type, filter, is_universal) - list_usage — list usage counts for sources across reports, blends, transfers, source groups, and overviews (requires source_ids) Start here when you need to understand what data is available before fetching it.
list-spaces
ChatGPTBrowse spaces (also known as "client folders"). Spaces are the top-level containers that organize reports and data sources. If a user says "space", "folder", or "client", they mean a space. Use action to choose the operation: - list — cursor-paginated list of spaces the user can access (pass cursor from page.cursor for next page) - show — full details for one space (report/measurement counts) - children — list sub-spaces under one space
list-templates
ChatGPTBrowse report templates — reusable report blueprints. Templates can be applied to create new reports. Linked reports auto-update when their template changes. Use action to choose the operation: - list — cursor-paginated list of team templates with tags and linked report counts (pass cursor from page.cursor for next page) - show — template details: pages with widget counts, theme settings - linked_reports — reports created from this template (auto-sync with template changes)
list-themes
ChatGPTBrowse report visual themes and color palettes. Control branding, colors, and visual appearance of reports. Use action to choose the operation: - list_themes — available themes for a report - list_colors — color palettes for a report
list-widgets
ChatGPTBrowse widgets on report tabs. Widgets are visual data components — charts, tables, single values, funnels, media, goals, etc. — that display marketing data from connected sources. If a user says "chart", "graph", "table", "KPI card", or "visualization", they mean a widget. Use action to choose the operation: - list — list all widgets in a report (summaries grouped by tab) - show — full widget details: type, configs with metrics/dimensions/source, layout - csv_export — export widget data as CSV rows - list_premade — cursor-paginated list of premade/template widgets (no report_id needed, pass cursor from page.cursor for next page). Requires channel_id to scope results to a specific integration
load-skill
ChatGPTLoad a workflow skill — a step-by-step playbook for a Whatagraph task that carries the correct workflow, field IDs, and gotchas. Skill names follow a predictable whatagraph-<domain> convention (e.g. whatagraph-widgets, whatagraph-blends, whatagraph-reports), and each write tool names its own skill in its description, so a known domain can be loaded directly here; use list-skills to discover skills when the name is unknown. Use action to choose the operation: - show — full skill content (markdown) - header — description + first 200 characters preview
manage-team
ChatGPTUpdate team name and settings. Use action to choose the operation: - update — update team name and/or localization settings (timezone, currency, decimal places, start of week, region, text direction) Playbook reference: whatagraph-team-and-members, available through load-skill. Documents parameters, identifiers and operation dependencies.
manage-upload-sessions
ChatGPTBrowser side-channel for getting local or pasted files (no URL) into the team's asset library. create — return a browser upload link the user opens in a new tab to upload files directly. Requires a target_scope (team, client, or report) plus the matching target_space_id or target_report_id where applicable — there is no silent team default. check — call after the user says they finished uploading; pass the token from create to get per-file results (added / failed) for the session.
preview-widget
ChatGPTRender a Whatagraph widget inline in the chat as a live preview. The chat host displays the actual widget (same charts and theme as in the report) inside its sandbox. Use widget_id from list-widgets (action=show or action=list). The widget renders with the report's current theme and the widget's saved date range, or a date_range_from / date_range_till override if supplied.
read-document
ChatGPTRead the extracted text of a document available to you, by its asset id (from list-assets). Use offset and limit to page through long files. Image and PDF attachments return a short pointer rather than text. Never guess a file's contents; read it.
remove-invitations
ChatGPTCancel a pending team invitation using action=cancel_invite and its invite_id. This invalidates that invitation. It does not remove an accepted team member or change their role. Pending invitation IDs are returned by the team-member management tool. Destructive actions. Every action of this tool: permanently deletes data. Breaks downstream: pending invites. These actions use a two-step server contract: the first call returns a preview without changes; executing the same arguments requires its single-use confirm_token. Playbook reference: whatagraph-deleting, available through load-skill. Documents parameters, identifiers and operation dependencies.
search-assets
ChatGPTHybrid search over the documents available to you — MySQL full-text keyword matching on extracted text, titles and summaries, plus semantic (vector) matching that catches paraphrases the keywords miss. In an agent conversation it is scoped to this conversation, your agent and the team; otherwise to the assets you can access (team-owned, plus spaces/reports you can reach). Returns matching assets (id, title, kind, summary). Use read-document to read a match's full text. Narrow with scope, kind, or filter_space_ids / filter_report_ids for exact-node ownership.
verify-source
ChatGPTAsk the provider, right now, whether one connected source is still reachable. Use this before telling a user a source is broken, because the stored status can be out of date in both directions. list-sources reports the stored access status as status, which is written when a fetch last failed and is not re-checked until someone verifies the source. A source that has since been fixed at the provider keeps reading error until then. This tool makes the live call instead, so it answers what is true now. It never changes a source's status. The stored access_status is left exactly as it was, whatever the probe finds, so it is always safe to call. Clearing a stale error still needs a person to press "Verify access" in the Whatagraph app. Read outcome rather than just reachable: - reachable — the provider listed the source under its own account. - reachable_via_other_account — another connected account can serve it, which is how the platform will fetch it. Working, despite this account not listing it. - not_available — the provider answered and did not list the source. This is a real problem and usually means access was removed at the provider. - provider_error — the provider could not be reached, so reachability is unknown. Read provider_error.next_steps, and retry later when provider_error.retryable is true. When stored_status_is_stale is true, the source works but is still stored as errored. Tell the user they can ignore the error, or press "Verify access" on that source to clear it.
view-creatives
ChatGPTSee the actual ad-creative images (Facebook, Google, LinkedIn, TikTok, ...) as images you can look at directly. Use this for creative analysis and creative QA — reviewing visual content, layout, contrast, typography, branding — instead of guessing from creative URLs or ad copy, which is all other tools return. Two ways to call it: - report_id: the creatives in a report's media widgets. Narrow with tab_id / widget_ids. Use list-widgets to find media widgets. - source_id: the creatives straight from a connected source, no report needed. Pass metrics, from, till, report_type when the source has several, and dimensions that include at least one creative image dimension (type creative_url in list-sources action=list_dimensions_and_metrics) plus a name dimension such as the ad name, which labels each image. Creatives are ranked by the first metric, highest first. Returns up to 10 creative images per call, each numbered and mapped to its ad name in the text block that comes first. If there are more creatives, the response says how many were left out — pass offset to page through them. Use export-report or fetch-data for the performance numbers to pair with what you see. When you present your analysis, show each creative to the user by embedding its URL from the mapping as a markdown image () next to what you say about it — the user cannot see the images you received.
view-goals
ChatGPTView data goals (called 'data goals' in the backend, 'goals' in the UI) — targets set on specific metrics to track progress toward KPIs. Use action to choose the operation: - list — paginated list of goals with optional search/filter by source - show — show details for a specific goal by ID
view-sharing
ChatGPTView report sharing settings and public share URLs. If a user says "share link", they mean this tool. Use action to choose the operation: - show — current sharing settings and share URL for a report URL types: The share_url is the public viewer URL (e.g. https://reports.live/shared/<hash>). This is NOT the signed-in editor URL (https://live.whatagraph.com/client/<space_id>/live-report/<report_id>).
view-team
ChatGPTView team settings, subscription details, available roles, and perform global search across the entire platform. Use the search action when you don't know which domain (reports, spaces, overviews) to look in. Use action to choose the operation: - show — team info: name, settings, enabled features - search — global cross-domain search: finds reports, overviews, and spaces matching a term - roles — available team roles (admin, editor, viewer, etc.) - show_subscription — current subscription plan and usage limits - list_plans — available subscription plans
delete-agents
Claudedelete-automations
Claudedelete-blends
Claudedelete-conversations
Claudedelete-custom-dimensions
Claudedelete-custom-metrics
Claudedelete-destinations
Claudedelete-filters
Claudedelete-goals
Claudedelete-overviews
Claudedelete-report-tabs
Claudedelete-reports
Claudedelete-sharing
Claudedelete-snapshots
Claudedelete-source-groups
Claudedelete-sources
Claudedelete-spaces
Claudedelete-templates
Claudedelete-themes
Claudedelete-widgets
Claudeexport-report
Claudefetch-data
Claudelist-agent-tools
Claudelist-agents
Claudelist-automations
Claudelist-blends
Claudelist-conversations
Claudelist-custom-dimensions
Claudelist-custom-metrics
Claudelist-destinations
Claudelist-external-connectors
Claudelist-filters
Claudelist-integrations
Claudelist-overviews
Claudelist-report-tabs
Claudelist-reports
Claudelist-skills
Claudelist-snapshots
Claudelist-source-groups
Claudelist-sources
Claudelist-spaces
Claudelist-templates
Claudelist-themes
Claudelist-widgets
Claudeload-skill
Claudemanage-agents
Claudemanage-automations
Claudemanage-blends
Claudemanage-conversations
Claudemanage-custom-dimensions
Claudemanage-custom-metrics
Claudemanage-destinations
Claudemanage-filters
Claudemanage-goals
Claudemanage-integrations
Claudemanage-members
Claudemanage-overviews
Claudemanage-report-tabs
Claudemanage-reports
Claudemanage-sharing
Claudemanage-snapshots
Claudemanage-source-groups
Claudemanage-sources
Claudemanage-spaces
Claudemanage-team
Claudemanage-templates
Claudemanage-themes
Claudemanage-widgets
Clauderemove-integrations
Clauderemove-members
Claudeview-goals
Claudeview-sharing
Claudeview-team
Claude
