add_report_analysis
ChatGPTAdd a written analysis as a static card at the top of one integration block of a report or dashboard. The card keeps the text exactly as written; it never refreshes with the data. WHEN TO CALL: Only when the user explicitly asks for the analysis to go INTO the report ("adiciona no relatório", "coloca essa análise lá"). Never on your own initiative, and never instead of answering in the chat. Reuse the analysis already written in this conversation. PARAMS — ASK THE USER IF MISSING, NEVER GUESS: - reportId: from the SCREEN CONTEXT section of the system prompt. Works for reports and dashboards alike. - sourceId: which integration block receives it, from get_report_data → sources[].source_id. - useArtifact: set it to true, and leave content empty, whenever the analysis the user wants is one you already rendered as an HTML artifact. The stored artifact is copied verbatim; rewriting it by hand always produces a different, poorer card, because artifacts are stripped from the history you receive. - content: only when there is no artifact. An HTML FRAGMENT styled with inline style="" attributes ONLY. No <!DOCTYPE>/ <html>/<head>/<body>, no <script>, no <style>, no external resources — script and style blocks are stripped before saving. No pseudo-elements, :hover or media queries; use real elements instead. Relative widths only, since the card resizes with the report grid. Emit the sections as TOP-LEVEL SIBLINGS and never wrap them in one container: the report flows them into side-by-side columns by itself. Always name the analysed period inside the text — the card is static, so on a dashboard the surrounding data keeps moving while the analysis does not. PREREQUISITES: get_report_data → the real figures and the sources[].source_id to write to.
compare_periods
ChatGPTCompare marketing metrics between two date ranges across ALL connected integrations of a project. Returns current values, previous values, absolute difference, and percentage change for key metrics from every platform — ideal for period-over-period analysis. WHEN TO CALL: Use when the user explicitly wants to compare two time periods. Examples: 'How did my metrics change compared to last month?', 'Compare this quarter vs last quarter for all platforms', 'What improved or declined since last period?', 'Show me month-over-month changes'. WHEN NOT TO CALL: - If the user wants comparison for a SINGLE integration only → use get_metrics_data with comparisonStart/comparisonEnd instead (more efficient, fewer API calls). - If the user wants just current values without comparison → use get_performance_summary instead. - If the user wants comparison grouped by category (social vs ads) → call get_channel_breakdown for each period separately, or use this tool for raw deltas. PREREQUISITES: Call list_projects first to get the projectId.
create_automation
ChatGPTCreate a new scheduled report automation for a project. The automation is ALWAYS created DISABLED. After creating, you MUST ask the user: "The automation was created disabled. Would you like to activate it now?" If they say yes, call toggle_automation with enabled=true. NOTIFICATION CHANNELS — Automations support THREE delivery channels that can be combined: - "email": Sends the report to one or more email addresses. Requires: recipients (email array), optionally emailSubject and emailReplyTo. - "in-app": Delivers a notification inside the Reportei platform. No extra parameters needed. - "whatsapp": Sends a report summary to a WhatsApp webhook URL. Requires: whatsappUrl (the webhook endpoint) and whatsappType ("text" for plain message, "json" for structured payload). Pass one or more channels in notificationChannels. They are combinable — e.g. ["email", "whatsapp"] means the report is sent via both email AND WhatsApp. Default: ["email"] if notificationChannels is not provided. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - notificationChannels: If the user mentions "send by WhatsApp" or "notify in the app", set the appropriate channels. If the user does not specify HOW they want to receive the report, ask: "How should the report be delivered? Options: email, WhatsApp, or in-app notification (Reportei platform). You can also combine them." - recipients (email array): REQUIRED when "email" is in notificationChannels. If missing, ask: "Which email address(es) should receive the report?" - whatsappUrl: REQUIRED when "whatsapp" is in notificationChannels. If missing, ask: "What is the WhatsApp webhook URL to send the report to?" - frequency (weekly/biweekly/monthly): If not specified, ask the user which frequency they want. - scheduleHour (e.g. 08:00): If not specified, ask what time of day they want the report sent. - sourceIds (integration IDs): If not specified, call list_integrations for the project and ask which integrations to include, or include all active ones if the user says "all". OPTIONAL PARAMS (can use defaults): - subtitle: Subtitle for the generated report. Pass an empty string when the user gave no subtitle. - templateId: If the user does not specify a template, use the default template from list_templates. - alertEmail: Single email for failure alerts. If omitted and email recipients provided, the first recipient is used automatically. Only ONE email allowed. - emailSubject: Custom subject line for email. Defaults to "{title} - Report". - emailReplyTo: Reply-to address for email. Defaults to first recipient. - whatsappType: "text" (default) or "json". Use "json" for structured webhook payloads. - frequencyWeekday (e.g. MO), frequencyOnThe (monthly), comparisonPeriod (1 or 2). WHEN TO CALL: Use when the user wants to schedule automatic report delivery. Examples: 'Set up a weekly report for my client', 'Create an automation that sends reports every Monday at 9am', 'Schedule monthly reports via WhatsApp', 'Create an automation with email and in-app notifications'. PREREQUISITES: Call list_projects (projectId), list_integrations (sourceIds), and optionally list_templates (templateId) first. NEXT STEP: After creation, ask the user whether to activate it via toggle_automation. PERMANENT ACTION: the automation is written to the account and, once activated, delivers reports to the configured email addresses and WhatsApp webhook on a recurring schedule. Deliveries cannot be recalled and this connector exposes no tool to delete the automation. Never create an automation to test or explore.
create_dashboard
ChatGPTCreate a new LIVE dashboard for a project using a template and one or more connected integrations. Dashboards refresh data dynamically every time they are viewed — they are NOT static like reports. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - integrationIds: Which integrations to include. If the user does not specify which platforms, call list_integrations for the project and ask which to include, or include all active ones if the user says "all". MUST be a JSON array: [123] not 123. - start / end: Date range for the dashboard. If not specified, ask the user which period to cover. OPTIONAL PARAMS (can use defaults): - templateId: If the user does not specify a template, use the default dashboard template from list_templates (pick one with "Dashboard" in the title). - comparisonStart / comparisonEnd: comparison period dates; must be provided together. WHEN TO CALL: Use when the user wants a permanent live dashboard. Examples: 'Create a live dashboard for Google Analytics and Search Console', 'Set up a real-time dashboard for my client's social media', 'Build a dashboard comparing this month vs last month for all ads platforms'. WHEN NOT TO CALL: - If the user wants a STATIC snapshot → use create_report instead. - If the user wants a quick temporary visual with specific metrics → use create_metrics_visualization instead (creates a temporary URL that auto-expires). - If the user wants to schedule recurring reports → use create_automation instead. PREREQUISITES: 1. list_projects → projectId 2. list_integrations → integrationIds (filter by projectId) 3. list_templates → templateId (optional, use default dashboard template if not specified) PERMANENT ACTION: the dashboard is written to the account, consumes the plan's dashboard quota and gets a shareable link. This connector exposes no tool to delete or undo it. Never create a dashboard to test or explore — validate every parameter with the read-only tools first. Returns the created dashboard with id, title, internal_url, and external_url.
create_goal
ChatGPTCreate a new KPI tracking goal for a project. Links a specific metric from a connected integration to a target value over a recurring time period. Once created, the goal tracks progress automatically and reports situation (on track/off track). The goal's CURRENT value is read from the data source during creation, so the goal already shows real progress right away. Never try to supply that number yourself. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - targetValue: The numeric target to reach. If the user says "set a goal" without specifying a number, ask: "What target value should the goal reach?" - referenceKey: The metric to track (from list_metrics, must be a number_v1 component). If the user says "track Instagram followers", call list_metrics for the integration slug to find the correct reference_key. Do NOT invent reference_keys. - frequency (weekly/monthly/quarterly/yearly): If not specified, ask which tracking period they want. - integrationSourceId: The source_id of the integration (from list_integrations). If not clear which integration, ask the user. WHEN TO CALL: Use when the user wants to set a target for a specific metric. Examples: 'Set a goal to reach 10000 Instagram followers this month', 'Track my Google Ads conversions with a target of 500', 'Create a KPI for website sessions'. PREREQUISITES: 1. list_projects → get projectId 2. list_integrations → get integrationSourceId (the source_id field, NOT the database ID) 3. list_metrics → get referenceKey (must be a number_v1 metric)
create_report
ChatGPTCreate a new STATIC report for a project using a template and one or more connected integrations. A report is a snapshot of data captured at creation time — it does NOT update automatically. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - integrationIds: Which integrations to include. If the user does not specify which platforms, call list_integrations for the project and ask which to include, or include all active ones if the user says "all". MUST be a JSON array: [123] not 123. - start / end: Date range for the report. If not specified, ask the user which period to cover. OPTIONAL PARAMS (can use defaults): - templateId: If the user does not specify a template, use the default template from list_templates. - comparisonStart / comparisonEnd: comparison period dates; must be provided together. WHEN TO CALL: Use when the user wants to generate a static report to share. Examples: 'Create a monthly report for my Instagram and Facebook', 'Generate a report for client X covering last month with comparison to the previous month', 'Build a report with all connected platforms for this quarter'. WHEN NOT TO CALL: - If the user wants a LIVE/dynamic view → use create_dashboard instead. - If the user wants a quick temporary visual with specific metrics → use create_metrics_visualization instead. - If the user wants to schedule recurring reports → use create_automation instead. PREREQUISITES: 1. list_projects → projectId 2. list_integrations → integrationIds (filter by projectId) 3. list_templates → templateId (optional, use default if not specified) PERMANENT ACTION: the report is written to the account, consumes the plan's report quota and gets a shareable link. This connector exposes no tool to delete or undo it. Never create a report to test or explore — validate every parameter with the read-only tools first. Returns the created report with id, title, internal_url, and external_url.
create_timeline_event
ChatGPTCreate a new timeline event (milestone or note) for a project. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - title: Short, descriptive label for the event (e.g. "Social Media Audit — February 2026"). If the user says "add a milestone" without specifying a title, ask: "What title should the milestone have?" - content: Event body as structured HTML. See CONTENT FORMATTING RULES below. Never pass an empty string. - projectId: If the user does not specify which project, ask. CONTENT FORMATTING RULES — ALWAYS FOLLOW: The content field is rendered as rich HTML. You MUST always produce well-structured HTML content, even if the user provides raw unformatted text. Structure the information yourself. Required formatting patterns: - Use <b> or <strong> for section headings and key terms (e.g. <b>Executive summary</b>) - Use <ul>/<li> for bullet-point lists (metrics, observations, strengths, weaknesses) - Use <ol>/<li> for ranked or ordered items (rankings, numbered recommendations) - Use <br> for line breaks between sections - Separate content into logical sections (e.g. Summary, Analysis per platform, Strengths, Weaknesses, Recommendations) Example of GOOD content structure: <b>Social Media Audit — February 2026</b><br> Platforms analyzed: Instagram Business · Facebook · LinkedIn<br><br> <b>Executive summary</b><br> <ul><li>Total Instagram reach: <b>2,924,322</b> (▼ 28.5% vs January)</li> <li>Instagram views: <b>3,707,517</b></li></ul> <b>Recommendations</b><br> <ol><li>Resume Instagram Stories — minimum 3 to 5 per week</li> <li>Increase Reels production</li></ol> Example of BAD content (never do this): Plain wall of text with no structure. Google Ads: volume drop impressions -40%, clicks -20%, but with quality improvement CTR went from 7.6% to 10.5%... For SIMPLE milestones (short annotations), a single sentence or the title text is acceptable. For ANALYTICAL or DESCRIPTIVE events, always apply full HTML structure as described above. OPTIONAL PARAMS: - reportId: Link the event to a specific report. Obtain from list_reports or create_report. - date: YYYY-MM-DD; defaults to today when omitted. WHEN TO CALL: Use when the user wants to log a milestone, note, or annotation. Examples: 'Log that we launched a campaign today', 'Add a milestone for the Black Friday campaign', 'Record that we changed the ad strategy on March 1st', 'Create a social media audit for February', 'Write an analysis of our Q1 ad performance'. PREREQUISITES: 1. list_projects → get projectId 2. (optional) list_reports → get reportId to link the event to a report
create_webhook
ChatGPTSubscribe to one or more webhook events by providing a callback URL and event types. Creates one subscription per event type. Available events: report_viewed, report_created, dashboard_created, automation_executed, control_goal_met, control_goal_not_met, timeline_milestone_added. CRITICAL PARAMS — DO NOT GUESS, ASK THE USER IF MISSING: - url: The callback URL that will receive POST requests. If the user has not provided a URL, ask: "What URL should receive the webhook notifications?" - events: Which event types to subscribe to. If the user has not specified which events, ask: "Which events should trigger the webhook?" and list the available event types. PROJECT SCOPE: Omitting project_id creates a company-wide webhook that receives events from every project. Users whose access is restricted to specific projects MUST pass project_id with one of those projects; call list_projects when unsure which ids are available. WHEN TO CALL: Use when the user wants to set up external notifications for Reportei events. Examples: 'Notify my server when a report is created', 'Send webhooks to https://example.com/hook for report_created and automation_executed', 'Subscribe to goal and automation events'. RELATED TOOLS: Call list_webhooks to see existing subscriptions; use delete_webhook to remove one.
delete_timeline_event
ChatGPTPermanently delete a timeline event by its ID. This action CANNOT be undone. You MUST confirm with the user before deleting. WHEN TO CALL: Use when the user explicitly asks to remove a timeline event. Examples: 'Remove the outdated milestone', 'Delete the timeline event I just created', 'Clean up old annotations for this project'. WARNING: Always confirm with the user before deleting: "Are you sure you want to delete this timeline event? This cannot be undone." PREREQUISITES: Call list_timeline_events first to find the event ID.
delete_webhook
ChatGPTPermanently remove a webhook subscription by ID. The URL will no longer receive notifications. This action CANNOT be undone. You MUST confirm with the user before deleting. PROJECT SCOPE: Company-wide webhooks (no project_id) can only be deleted by users who reach every project in the company, since removing one stops notifications for projects they may not have access to. WHEN TO CALL: Use when the user explicitly asks to remove a webhook subscription. Examples: 'Remove webhook 123', 'Unsubscribe from this webhook', 'Delete the webhook for report_created'. WARNING: Always confirm with the user before deleting: "Are you sure you want to delete this webhook? This cannot be undone." PREREQUISITES: Call list_webhooks first to get the webhook id.
get_audience_insights
ChatGPTAudience demographic data (age, gender, country, city, location) across connected SOCIAL MEDIA platforms only. Returns demographic breakdowns from platforms that provide audience data: Instagram, Facebook, YouTube, LinkedIn, and TikTok. Does NOT include ads platforms or web analytics. WHEN TO CALL: Use when the user asks about who their audience is, demographics, or follower profiles. Examples: 'What is my audience demographic?', 'What age groups follow me on Instagram?', 'Where are my followers located?', 'What is the gender split of my social media audience?', 'Compare audience demographics across platforms'. WHEN NOT TO CALL: - If the user wants performance KPIs (followers count, engagement rate) not demographics → use get_performance_summary instead. - If the user wants top posts/content → use get_top_content instead. - If the user wants demographic data from ONE specific platform → use get_metrics_data with demographic reference_keys instead. PREREQUISITES: Call list_projects first to get the projectId.
get_automation
ChatGPTGet full details of a single automation: schedule, notification channels and their config, recipients, WhatsApp settings, last run, sources (integrations), template, period, and comparison period. Returns notification_channels (array of active channels: "email", "in-app", "whatsapp"), email recipients (if email channel active), whatsapp_url and whatsapp_type (if whatsapp active). WHEN TO CALL: Use when the user asks about a specific automation's configuration. Examples: 'What are the settings for automation X?', 'Who receives this automated report?', 'Which integrations are included in this automation?', 'How is this automation notifying?'. PREREQUISITES: Call list_automations first to get the automation id.
get_campaign_summary
ChatGPTAggregated advertising (paid media) performance across all connected ADS platforms for a project. Covers Facebook Ads, Google Ads, LinkedIn Ads, TikTok Ads, Pinterest Ads, Twitter Ads, Microsoft Ads, and Spotify Ads. Returns ads-specific KPIs: spend, impressions, clicks, CTR, CPC, CPM, conversions, ROAS, and cost-per-conversion unified in a single response. This tool ONLY includes ads/paid platforms — no social organic, no web analytics, no CRM. WHEN TO CALL: Use when the user asks specifically about advertising, paid media, or campaign performance. Examples: 'How much am I spending on ads across all platforms?', 'What is my overall ROAS?', 'Compare ad performance between Google and Facebook', 'Give me a summary of all paid campaigns', 'What is my total ad spend this month?'. WHEN NOT TO CALL: - If the user wants performance across ALL channel types (social + ads + analytics + CRM) → use get_channel_breakdown instead. - If the user wants a broad overview of everything → use get_performance_summary instead. - If the user wants a specific metric from ONE ads platform → use get_metrics_data with that integration instead. - If the user wants to compare ads vs organic social → use get_channel_breakdown (it groups by category). PREREQUISITES: Call list_projects first to get the projectId.
get_channel_breakdown
ChatGPTPerformance breakdown grouped by marketing channel CATEGORY: social_media, ads, web_analytics, crm, ecommerce, and email_marketing. Each category aggregates KPIs from all connected integrations of that type for a project. Use this when the user wants to compare different types of channels against each other. WHEN TO CALL: Use when the user wants to compare channel categories or understand which type of marketing is performing best. Examples: 'How do my ads compare to my organic social?', 'Break down performance by channel type', 'Which category is performing best?', 'Compare social vs paid vs email marketing results'. WHEN NOT TO CALL: - If the user wants a flat overview of ALL platforms without category grouping → use get_performance_summary instead. - If the user asks specifically about ADS only (spend, ROAS, CTR) → use get_campaign_summary instead (faster, ads-focused). - If the user wants a specific metric from one integration → use get_metrics_data instead. PREREQUISITES: Call list_projects first to get the projectId.
get_company_settings
ChatGPTRetrieve the authenticated company profile and settings. Returns: id, name, logo, type, total_clients (number of projects), and company_specialty. TERMINOLOGY: A "company" is the top-level account in Reportei. It owns multiple projects (clients). WHEN TO CALL: Use to verify authentication, check company context, or answer questions about the company itself. Examples: 'How many projects do I have?', 'What is my company name?', 'What type of company am I?', 'What is my company specialty?'. NEXT STEPS: Call list_projects to see individual projects within the company.
get_custom_table_data
ChatGPTCompose and execute a fully customized datatable query for a single integration using a custom set of metrics and dimensions, then return the rows. Nothing is persisted — no widget, table, report or dashboard is created or modified. Use this tool when: - The user needs insights from a table with a combination of columns that does not match any existing preset (e.g. "show campaigns by spend, CPM and frequency" when no preset has all three). - You want to reason over richer or more focused data than what is already in the report before giving your answer. Workflow: 1. Call list_table_fields(integrationSlug) to discover valid metric keys, dimension keys, and available preset reference_keys for this integration type. 2. Pick a reference_key from datatable_presets as the base (it carries the correct query template for G4 — do not invent reference_keys). 3. Call this tool with the reference_key plus your chosen metric/dimension keys. IMPORTANT — nothing is altered: This is an internal read-only query. The user's reports, dashboards, and widgets are never touched. Use the returned data to reason and craft your answer, then discard it. Returns: { spec_used, rows, rows_total, rows_truncated } on success. { error: true, type, message } on failure. Error types: not_found, not_editable, invalid_reference_key, invalid_metrics, invalid_dimensions, too_many_metrics, too_many_dimensions.
get_dashboard
ChatGPTRetrieve full details of a single dashboard by its ID, including shareable URLs. Returns: id, title, subtitle, start_date, end_date, comparison_start_date, comparison_end_date, template_id, client_id, created_at, internal_url, and external_url. WHEN TO CALL: Use when the user wants details about a specific dashboard. Examples: 'Get the link to dashboard X', 'What period is this dashboard showing?'. The external_url can be shared with clients for a live, always-updated view. PREREQUISITES: Call list_dashboards first to find the dashboard ID.
get_goal_progress
ChatGPTDetailed progress data for a specific tracked KPI goal: current value, target, percentage completion, estimated end value, situation assessment, days remaining, and recent value history. WHEN TO CALL: Use when the user asks about detailed progress on a specific goal. Examples: 'How close am I to reaching my Instagram follower goal?', 'What is the progress on my Google Ads conversion goal?', 'Am I on track to hit my monthly target?', 'Show me detailed goal progress'. WHEN NOT TO CALL: - If the user wants a summary of ALL goals → use list_goals instead. PREREQUISITES: Call list_goals first to find the tracked_metric_id.
get_help_article
ChatGPTFetch the full Markdown content of a help-center article by its slug. The slug must come from the catalog listed in the system prompt or from a previous search_help_center call — do NOT guess or invent slugs. Returns: { found: true, slug, title, content } on success. { found: false, error } when the article does not exist. After retrieving the content, summarise it in plain language for the user. Do NOT dump the raw Markdown verbatim — always paraphrase or highlight the key steps relevant to the user's question.
get_integration
ChatGPTRetrieve full details of a single connected integration (account / data source / network) by its ID. Returns: id, name, slug, status ("active" or "inactive"), project_id, project_name, created_at, and updated_at. TERMINOLOGY: "account", "network", "source" all refer to integrations. WHEN TO CALL: Use when the user asks about a specific integration's details. Examples: 'Is my Facebook Ads integration active?', 'When was this integration connected?', 'Which project does this account belong to?'. PREREQUISITES: Call list_integrations first to find the integration ID. NEXT STEPS: Use the slug from the response with list_metrics to discover available metrics.
get_metrics_data
ChatGPTFetch actual numeric/chart/table data for one or more SPECIFIC metrics of a SINGLE connected integration (account/source/network) within a date range. This is the most granular data tool — it fetches exact metrics you choose from exactly one integration. TERMINOLOGY: integrationId refers to a connected account/source (from list_integrations), NOT a project/client ID. IMPORTANT — METRICS FORMAT: Each object in the metrics array MUST be passed exactly as returned by list_metrics. Do NOT add, remove, or modify any fields. Only include fields that list_metrics returned for that metric. If list_metrics returned dimensions, sort, custom, type, or is_funnel_events, include them as-is. If list_metrics did NOT return a field, do NOT include it (no empty arrays or nulls). WHEN TO CALL: Use when the user asks about specific metrics from a specific platform, or needs granular control over which data to fetch. Examples: 'How many followers did I gain this month on Instagram?', 'What was my ad spend on Facebook Ads specifically?', 'What is my website traffic trend on GA4?', 'How did my Instagram engagement change compared to last month?', 'What is my Google Ads ROAS for this quarter?'. WHEN NOT TO CALL: - If the user wants an overview across ALL platforms at once → use get_performance_summary instead (no need to call list_metrics first). - If the user wants to compare channel categories → use get_channel_breakdown instead. - If the user wants only ads/paid metrics across all ad platforms → use get_campaign_summary instead. - If the user wants top posts/content → use get_top_content instead. - If the user wants audience demographics across platforms → use get_audience_insights instead. CRITICAL PARAMS: The metrics array MUST NOT be invented. You MUST call list_metrics first to get valid metric objects. If the user has not specified which metrics they want, ask them or call list_metrics to discover what is available before calling this tool. PREREQUISITES: 1. list_integrations → get integrationId 2. list_metrics → get metric objects (pass the slug from the integration) 3. Then call this tool with those exact metric objects. Returns metric values keyed by reference_key. Errors are returned inline as {type: "no_data_in_period"}, {type: "expired_token"}, or {type: "invalid_metrics_combination"}. Optionally provide comparisonStart/comparisonEnd for period-over-period comparison on a single integration.
get_opportunity_score
ChatGPTGet REPORTEI'S OWN opportunity score for a project (client), computed by Reportei from the Meta Ads data it has already collected. This is not the score Meta shows inside Ads Manager, and the two numbers are not expected to match. The score highlights how much optimization opportunity exists in the connected Meta Ads account selected by Reportei's opportunity score logic. This tool is read-only: it never applies recommendations or changes campaigns. WHEN TO CALL: Use when the user asks for an optimization score, opportunity score, improvement potential, or quick health check for Meta Ads on a specific project. This is the default for a bare "opportunity score" request. PREREQUISITES: Call list_projects first to get the projectId. NEXT STEP: Call get_recommendations with the same projectId to inspect the recommended actions.
get_performance_summary
ChatGPTAggregated KPI summary from ALL connected integrations of a project for a date range. Returns key numeric metrics (followers, engagement, reach, spend, clicks, sessions, etc.) grouped by platform in a flat list — all in a single call instead of querying each integration individually. This is the broadest overview tool available. WHEN TO CALL: Use for broad, cross-platform overviews. Examples: 'Give me an overview of all my marketing performance', 'How is my client doing across all channels?', 'Summarize this month's marketing KPIs', 'What are the key numbers for project X?'. WHEN NOT TO CALL: - If the user wants metrics grouped by CATEGORY (social vs ads vs analytics) → use get_channel_breakdown instead. - If the user asks specifically about ADS performance (spend, ROAS, CTR) → use get_campaign_summary instead. - If the user wants a specific metric from ONE integration → use get_metrics_data instead. - If the user wants period-over-period comparison with deltas → use compare_periods instead. - If the user wants top posts/content → use get_top_content instead. - If the user wants audience demographics → use get_audience_insights instead. PREREQUISITES: Call list_projects first to get the projectId.
get_project
ChatGPTRetrieve full details of a single project (client) by its ID. Returns: id, name, logo, timezone, locale, date_format, and decimal_separator_format. TERMINOLOGY: "project", "projeto", "client", "cliente" refer to projects. "account", "conta", "network", "rede", "source" refer to integrations — use get_integration instead. WHEN TO CALL: Use when the user asks about a specific project's settings. Examples: 'What timezone is client X using?', 'What locale and date format does this project use?'. PREREQUISITES: Call list_projects first to find the project ID.
get_recommendations
ChatGPTGet Meta Ads optimization recommendations for a project (client), based on REPORTEI'S OWN opportunity score data — not on what Meta's Ads Manager is currently recommending. Recommendations may include affected campaign/ad objects when includeObjects is true. This tool is read-only: it never applies recommendations or changes campaigns. WHEN TO CALL: Use when the user asks what to improve, which optimizations are recommended, or why the Meta Ads opportunity score can be improved. WHEN NOT TO CALL: Do not use this tool to apply recommendations. The MCP intentionally exposes no apply/mutation action for Meta Ads recommendations. PREREQUISITES: Call list_projects first to get the projectId.
get_report
ChatGPTRetrieve full details of a single report by its ID, including shareable internal and external URLs. Returns: id, title, subtitle, start_date, end_date, comparison_start_date, comparison_end_date, template_id, client_id, created_at, internal_url, and external_url. WHEN TO CALL: Use when the user wants details about a specific report. Examples: 'Get the shareable link for report X', 'What period does this report cover?'. The external_url can be shared with clients who do not have a Reportei account. PREREQUISITES: Call list_reports first to find the report ID.
get_report_analysis
ChatGPTRead back the exact HTML of an analysis card already on a report or dashboard. WHEN TO CALL: before editing a card. It is the ONLY way to see what is on the report — you cannot recall it, and rewriting from memory always loses the design. Read it, then call update_report_analysis with replacements to change just the part the user asked about. Omit widgetId when the report has a single analysis card.
get_report_data
ChatGPTRetrieve the ACTUAL metric VALUES (widget data) of an existing report OR dashboard by its ID. Unlike get_report (which returns only metadata), this returns the numbers the user sees on screen: KPI values with period-over-period comparison, chart series, and table rows, grouped by integration (Facebook, Instagram, Google Ads, etc.). WHEN TO CALL: - The user refers to "this report", "this dashboard", "esse relatório", or the data on screen (the SCREEN CONTEXT section of the system prompt provides the reportId when applicable). - The user asks you to analyze, summarize, comment on, or compare the metrics of a specific existing report/dashboard. Examples: 'What do you think about this report?', 'Resuma os números desse relatório', 'Which metric grew the most here?', 'Compare os canais desse dashboard'. WHEN NOT TO CALL: - To fetch fresh/live metrics not tied to an existing report → use get_metrics_data. - For report metadata only (title, dates, share link) → use get_report. PARAMS: - reportId (required): numeric ID of the report or dashboard. - sourceId (optional): restrict the response to a single integration's source_id (from the report's own sources) when the report is large and you only need one platform. - sortByColumn (optional): a column name from a table's columns list (e.g. "results", "spend", "cost_per_results"). Sorts EVERY in-scope table that has that column by its numeric value over the table's FULL rows (before sampling) and returns the top of the sorted order — so you get the TRUE highest/lowest even from a rows_truncated table. Non-numeric/empty cells sort last. Pair with sourceId to scope to one integration. - descending (optional): direction for sortByColumn. true (default) = highest first ("most/best/top"); false = lowest first ("cheapest/fewest/worst"). RESPONSE SHAPE: sources[] lists EVERY integration in the report (always complete, never truncated) — each with platform (e.g. "Instagram Business", "Facebook", "YouTube", "Pinterest"), account_name, data_status, and its widgets. To answer "which integrations/networks are in this report", read sources[].platform and EXCLUDE any entry flagged is_custom_block:true (a consolidated summary block, not a network). PERIOD & DATA FRESHNESS: report.start_date/end_date are the CURRENT analysis period and report.data_synced_at is when the data was last synced. State the period from these fields — NEVER invent, guess, or carry over a date range from another report. A dynamic dashboard's period can legitimately be a single day (e.g. a "week-to-date" view on a Monday). If data_synced_at is clearly older than the period end (the data was not refreshed for the current window), do NOT present the figures as the current period's data — say plainly that the latest available data is from data_synced_at. WIDGET TYPES: each widget has a type — number (single KPI, may include a comparison), chart (time series in labels+series), table (a columns list naming each column, then rows; each row's values are POSITIONAL — value at index N belongs to columns[N]; may be rows_truncated), or funnel (an ORDERED list of steps[], each a stage with its own label+value, e.g. content views → add to cart → leads → purchases). A funnel step already gives the report's EXACT aggregate for that stage. PREFER a direct aggregate (a number KPI or a funnel step) over summing table rows — table rows may be truncated (rows_truncated:true), so summing them undercounts. Only sum table rows when no direct aggregate for that metric exists, and if the table is truncated say the sum is a partial/visible total, not the real total. READING A TABLE: row values are positional — to read a metric, find it in columns and take the value at that same index in each row (some cells are objects like {value, title} where title names the result type; use value for math). A cell's value is the literal figure shown on screen for that column. RANKING / SUPERLATIVES ("which campaign/ad/row has the highest/lowest/best/worst X?", "top/worst N"): This is a MANDATO…
get_timeline_event
ChatGPTRetrieve full details of a single timeline event by its ID. Returns: id, title, content (HTML), project_id, report_id, date, created_at, and updated_at. WHEN TO CALL: Use when the user wants the full content of a specific event. Examples: 'Get details of timeline event X', 'What is the full content of this milestone?', 'Which report is this event linked to?'. PREREQUISITES: Call list_timeline_events first to find the event ID.
get_top_content
ChatGPTTop-performing posts and content ranked by engagement across SOCIAL MEDIA platforms only. Returns media/content data tables from social integrations: Instagram, Facebook, YouTube, LinkedIn, TikTok, Pinterest, and Threads. Does NOT include ads platforms or web analytics. WHEN TO CALL: Use when the user asks about their best posts, top content, or content performance. Examples: 'What were my best performing posts this month?', 'Show me top content across all social channels', 'Which posts got the most engagement?', 'What content performed best on Instagram?'. WHEN NOT TO CALL: - If the user asks about ADS campaigns or ad creatives → use get_campaign_summary instead. - If the user wants numeric KPIs (followers, reach) not post-level content → use get_performance_summary instead. - If the user wants a specific metric from one social platform → use get_metrics_data instead. PREREQUISITES: Call list_projects first to get the projectId.
list_automations
ChatGPTList all report automations for a project. Returns id, title, status (enabled/disabled), frequency (weekly/biweekly/monthly), notification channels, schedule, next run time, and last run. TERMINOLOGY: An "automation" is a scheduled job that automatically generates and delivers a report to recipients at a recurring interval. Delivery can happen via three channels: - "email": report sent to email addresses - "in-app": notification inside the Reportei platform - "whatsapp": report summary sent to a WhatsApp webhook URL Multiple channels can be active simultaneously (e.g. email + whatsapp). WHEN TO CALL: Use when the user asks about scheduled/automatic reports for a project. Examples: 'What automations are set for this project?', 'When does the next report get sent?', 'List scheduled report automations'. RELATED TOOLS: Use get_automation for full details of a specific automation, create_automation to add one, toggle_automation to enable/disable, update_automation to change settings. PREREQUISITES: Call list_projects first to get the projectId.
list_dashboards
ChatGPTList dashboards (live/dynamic data views) for the authenticated company. Unlike reports (static snapshots), dashboards refresh data automatically every time they are viewed. TERMINOLOGY: A "dashboard" in Reportei is a LIVE view that always shows up-to-date data. Reports are static snapshots. If the user says "dashboard" or "live view", use this tool. If the user says "report", use list_reports instead. WHEN TO CALL: Use when the user asks about existing dashboards or live views. Examples: 'Show me all live dashboards', 'Which dashboards does client X have?', 'Do I have any dashboards for this project?'. RELATED TOOLS: Use get_dashboard for full details, create_dashboard to create a new one. PREREQUISITES: Call list_projects first to get the projectId for filtering.
list_goals
ChatGPTList all tracked KPI goals for a project with their current situation. Each goal tracks a specific metric from a connected integration over a recurring time period with a target value. Returns goal ID, metric reference_key, source info, frequency, current value, target, progress percentage, and situation (high/ideal/average/low/no_data). TERMINOLOGY: A "goal" (also "KPI goal" or "tracked metric") is a target set for a specific metric (e.g. "reach 10000 Instagram followers this month"). Goals track progress automatically. WHEN TO CALL: Use when the user asks about goals, targets, KPIs, or tracking status. Examples: 'What goals are set for this project?', 'Which KPIs are being tracked?', 'Are we on track to meet our goals?', 'Show me all active goals and their status'. RELATED TOOLS: Use get_goal_progress for detailed progress on a specific goal, create_goal to add a new one, update_goal to change target or alerts. PREREQUISITES: Call list_projects first to get the projectId.
list_integrations
ChatGPTList connected integrations (accounts / data sources / networks) for the authenticated company. Each entry returns: id, name, slug (e.g. "facebook_ads"), status ("active" or "inactive"), project_id, project_name, created_at, and updated_at. IMPORTANT: a project can hold several distinct accounts that share the same display name (e.g. three separate Meta Ads accounts all named "Reportei"). They are different integrations with different ids — list every one of them separately and never merge same-named entries into a single item. TERMINOLOGY: When the user mentions "account", "network", "source", or "data source", they are referring to integrations — use this tool. Do NOT use list_projects for these terms. Projects (clients) are a different concept: they group multiple integrations together. WHEN TO CALL: Use when the user asks about connected platforms, or as a prerequisite step to resolve integration IDs needed by other tools. Examples: 'Which platforms is my client connected to?', 'Do I have Google Ads connected?', 'Show me all Instagram accounts', 'Which networks are active for project X?'. NEXT STEPS: After getting integration IDs, use the slug with list_metrics to discover available metrics, or pass IDs to get_metrics_data, create_report, or create_dashboard. PREREQUISITES: Call list_projects first to get the projectId for filtering. PAGINATION: the response's meta.last_page tells you how many pages exist. When it is greater than 1 you have NOT seen every row — request the next pages before answering anything that depends on the full list (counts, "all of them", picking one to act on).
list_metrics
ChatGPTDISCOVERY tool: list all available metrics (widgets) for a given integration type identified by its slug. This tool does NOT fetch data — it returns the CATALOG of what can be fetched. Use the metric objects returned here as input to get_metrics_data to retrieve actual values. TERMINOLOGY: Metrics belong to integration TYPES (e.g. "facebook_ads", "instagram_business"), not to projects (clients). A "slug" identifies the platform type, not a specific connected account. Returns a paginated array where each entry contains: id, reference_key (e.g. "fb_ads:spend"), component (number_v1, chart_v1, or datatable_v1), metrics, dimensions, sort, and type. SEARCH: a platform can have hundreds of metrics. When looking for something specific, pass search (e.g. "spend", "followers", "clicks") instead of reading the catalog page by page. PAGINATION: the response's meta.last_page tells you how many pages exist. When it is greater than 1 you have NOT seen every metric — use search or request the next pages before concluding that a metric is not available. WHEN TO CALL: Use when the user asks what metrics are available, or before calling get_metrics_data to discover valid reference_keys. Examples: 'What metrics can I pull from Instagram?', 'Which KPIs are available for Google Ads?', 'What data can I get from Facebook Ads?', 'Show me all available YouTube metrics'. WHEN NOT TO CALL: - If the user wants actual metric VALUES (not discovery) → use get_metrics_data after calling this tool. - If the user wants a quick aggregated overview → use get_performance_summary or get_campaign_summary (they auto-select relevant KPIs without needing to discover metrics first). PREREQUISITES: Call list_integrations first to find the integration slug. NEXT STEP: Pass the metric objects returned here directly to get_metrics_data.
list_projects
ChatGPTList projects (clients) for the authenticated company. This is typically the FIRST STEP in any workflow — most other tools require a projectId. TERMINOLOGY: When the user mentions "project", "projeto", "client", or "cliente", they refer to projects — use this tool. A project groups multiple integrations (accounts/sources) together. Do NOT use this tool when the user asks about "account", "conta", "network", "rede", or "source" — those refer to integrations; use list_integrations instead. Each entry returns: id, name, logo, timezone (e.g. "America/Sao_Paulo"), locale (e.g. "pt_br"), date_format, and decimal_separator_format. WHEN TO CALL: Use when the user asks about their clients/projects, or as the first step to resolve a projectId needed by other tools. Examples: 'Show me all my clients', 'Which projects do I manage?', 'How many clients do I have?', 'Find the project for client X'. NEXT STEPS: After getting a projectId, call list_integrations to see connected platforms, list_reports/list_dashboards for existing outputs, or any analytics tool for performance data. PAGINATION: the response's meta.last_page tells you how many pages exist. When it is greater than 1 you have NOT seen every project — request the next pages before answering anything that depends on the full list.
list_reports
ChatGPTList generated reports (static data snapshots) for the authenticated company. Each entry returns: id, title, subtitle, start_date, end_date, comparison_start_date, comparison_end_date, template_id, client_id, created_at, internal_url, and external_url. TERMINOLOGY: A "report" in Reportei is a STATIC snapshot of marketing data captured at creation time. It does NOT update automatically. For live/dynamic data views, use dashboards instead. WHEN TO CALL: Use when the user asks about existing reports, wants to find a report link, or wants to see report history. Examples: 'Show me recent reports for client X', 'What reports were created this month?', 'How many reports does this project have?', 'Find the latest report'. WHEN NOT TO CALL: - If the user wants live/dynamic views → use list_dashboards instead. - If the user wants to fetch raw metric data → use get_metrics_data or get_performance_summary. RELATED TOOLS: Use get_report for full details, create_report to generate a new one. PREREQUISITES: Call list_projects first to get the projectId for filtering.
list_table_fields
ChatGPTDISCOVERY tool: list all combinable metrics and dimensions available for a given integration type, along with its datatable presets (reference_keys you can use as the base for get_custom_table_data). Use this tool when you want to query a table with a CUSTOM set of columns that is different from what the report already shows. For example, if the user asks "compare campaigns by spend, impressions and CPM" and no existing preset already contains exactly those columns, call this tool first to verify the available metric keys, then call get_custom_table_data to fetch the result. Returns: - editable: whether this integration type supports column customization - datatable_presets: existing table presets (reference_key, default columns) - available_metrics: map of metric_key => label (all combinable columns) - available_dimensions: map of dimension_key => label (grouping/breakdown keys) WHEN NOT TO CALL: - If a preset from list_metrics already has the exact columns needed, use get_metrics_data directly — no need for custom composition. PREREQUISITES: Call list_integrations first to obtain the integration slug. NEXT STEP: Pass a reference_key from datatable_presets + chosen metric/dimension keys to get_custom_table_data.
list_templates
ChatGPTList report and dashboard templates available for the authenticated company. Each entry returns: id, title, description, kind, is_default, created_at, and updated_at. TERMINOLOGY: A "template" defines the layout and widget configuration for reports and dashboards. Use "kind" to route the template: kind "report" is for create_report and create_automation, kind "dashboard" is for create_dashboard. The entry with "is_default": true is the platform-provided starter layout for that kind — use it whenever the user does not state a template preference. FINDING THE DEFAULT: results always start with the default templates, so the first page contains one entry with "is_default": true for each kind. Select it by the is_default flag and the kind you need — never by matching the title text, which is localized (it reads "Padrão" in Portuguese). WHEN TO CALL: Use when the user asks about available templates, or as a prerequisite for create_report, create_dashboard, or create_automation when a template id is needed. Examples: 'Which templates can I use for a report?', 'What dashboard templates are available?', 'Show me my custom templates'. RELATED TOOLS: Pass the template id to create_report, create_dashboard, or create_automation.
list_timeline_events
ChatGPTList timeline events (milestones, notes, or annotations) for the authenticated company. Each entry returns: id, title, content (HTML string), project_id, report_id (if linked), date (YYYY-MM-DD), created_at, and updated_at. TERMINOLOGY: A "timeline event" is a user-created milestone, note, or annotation recorded for a project. It can optionally be linked to a specific report. Also known as "milestone", "note", "annotation", or "event". WHEN TO CALL: Use when the user asks about milestones, events, notes, or timeline history. Examples: 'What milestones happened for client X?', 'Show me the timeline for this month', 'Which events are linked to this report?', 'What happened on this date for my project?'. RELATED TOOLS: Use get_timeline_event for full details, create_timeline_event to add new ones, update_timeline_event to modify, delete_timeline_event to remove. PREREQUISITES: Call list_projects first to get the projectId for filtering.
list_webhooks
ChatGPTList all webhook subscriptions for the authenticated company. Returns each webhook's id, url, event_type, project_id (if scoped), status, created_at, updated_at. TERMINOLOGY: A "webhook" is a subscription that sends HTTP POST notifications to an external URL when specific events occur in Reportei. Each subscription covers one event type. Available event types: report_viewed, report_created, dashboard_created, automation_executed, control_goal_met, control_goal_not_met, timeline_milestone_added. A webhook with no project_id is company-wide: it receives events from every project. Users restricted to some projects see their own project webhooks plus the company-wide ones, but can only manage the project-scoped ones. WHEN TO CALL: Use when the user asks about webhook configurations or notifications. Examples: 'What webhooks are configured?', 'Which URLs receive report_created notifications?', 'List my webhook subscriptions'. RELATED TOOLS: Use create_webhook to add new subscriptions, update_webhook to modify, delete_webhook to remove.
remove_report_analysis
ChatGPTDelete an analysis card from a report or dashboard. Only cards added through the chat can be removed; native metric widgets are untouched. Pass widgetId when you know it (add_report_analysis returns it); omit it and the report's only analysis card is removed, or you get the list of candidates back to choose from. Confirm with the user before calling, and never claim you cannot do it — this tool exists.
run_company_analysis
ChatGPTAggregate, rank, total or compare metrics across MULTIPLE projects (clients) of the company in a single call. Use this instead of looping per-project tools (get_campaign_summary, get_metrics_data, etc.) when the user asks something that needs data from many projects. WHEN TO CALL: - "Which project spent the most on X?" → aggregation=ranking with the right metric_keys. - "Total Y across all my clients" → aggregation=total. - "Compare metric A vs B in all projects" → aggregation=comparison with multiple metric_keys. - "Top 10 projects by Z" → aggregation=ranking, sort=desc, limit=10. WHEN NOT TO CALL: - Single-project questions → use get_metrics_data, get_campaign_summary, etc. - Time series across projects → not supported in v1. - Calculated/derived metrics (ROAS, CTR, conversion rate) → not supported in v1, request the base metrics and combine them yourself when possible. BEHAVIOR: This tool returns immediately with {status: "queued"} and a short summary. The actual answer is produced asynchronously and arrives in this same thread once the analysis is complete (can take a few minutes for accounts with many projects). The chat input stays locked while the background job runs. ===================================================================== FAST-PATH: USE A PRESET INSTEAD OF DISCOVERING metric_keys ===================================================================== For recurring cross-project questions you should use a preset — a curated bundle of reference_keys baked into the server. Presets are MORE RELIABLE than guessing metric_keys via list_metrics and SHOULD ALWAYS BE PREFERRED when one matches the user's question. AVAILABLE PRESETS: - "ads_spend" — total amount spent on paid ads across every supported network (Facebook Ads, Google Ads, TikTok Ads, LinkedIn Ads, Pinterest Ads, Microsoft Ads, Twitter Ads, Spotify Ads). Use it whenever the user asks about ads investment / spend / budget across projects. Examples: - "Qual projeto teve maior investimento em ads?" → preset="ads_spend", aggregation="ranking", sort="desc" - "Total gasto em anúncios no mês passado" → preset="ads_spend", aggregation="total" - "Top 5 clientes por investimento em mídia paga" → preset="ads_spend", aggregation="ranking", limit=5 When using a preset, leave metric_keys EMPTY ([]). The preset expands to the right reference_keys on the server side. ===================================================================== PARAMETERS: - preset (optional): one of the curated bundles above (e.g. "ads_spend"). When set, metric_keys must be empty/omitted — the preset supplies them. - metric_keys: array of V4Config reference_keys, e.g. ["fb_ads:spend", "gads:cost_micros"]. Use this ONLY when no preset fits. Call list_metrics(integration_slug) first if you don't know the exact keys. Only number_v1 (scalar) widgets are supported. - aggregation: one of ranking, total, breakdown, comparison. - start_date / end_date: YYYY-MM-DD. - filters (optional): { integration_types?: int[], project_ids?: int[], max_projects?: int }. - sort: desc (default) or asc — only meaningful for ranking. - limit (optional): cap on result rows — only meaningful for ranking. - group_by: project (default) or source_type — only meaningful for breakdown. ERRORS: - invalid_preset: preset name does not exist. Inspect available_presets and retry. - invalid_metric_key: reference_key does not exist. Inspect suggestions and retry. - unsupported_widget_type: the requested metric is not scalar (chart/datatable). Pick a number_v1 widget instead. - invalid_period: dates are malformed or out of order. - invalid_aggregation: unknown aggregation strategy.
search_help_center
ChatGPTSearch the Reportei help center knowledge base for articles matching a keyword or topic. Returns up to 5 results, each with a slug, title and one-sentence summary. Use this tool FIRST when the user asks a how-to question about the Reportei platform (e.g. "how do I create a template?", "why are my Instagram impressions not loading?"). After finding a relevant slug, call get_help_article to fetch the full content before answering. If no results are returned for a specific query, broaden the search term (e.g. "impressões" → "instagram métricas") and try once more. WHEN NOT TO CALL: - For data/analytics questions (use the metrics/report tools instead). - For billing disputes, account access issues or bug reports — emit [CONTACT_SUPPORT] so the user can reach a human agent.
toggle_automation
ChatGPTEnable or disable an automation. When enabled, the automation is registered with the scheduler and will run at the next scheduled time. When disabled, no reports are sent. Idempotent: enabling an already enabled (or disabling an already disabled) automation does not error. WHEN TO CALL: Use when the user wants to activate, deactivate, pause, or resume an automation. Also called automatically after create_automation when the user confirms activation. Examples: 'Turn on automation X', 'Disable this automation', 'Pause the weekly report', 'Activate the automation I just created'. PREREQUISITES: Call list_automations to get the automation id.
update_automation
ChatGPTUpdate an existing automation. PATCH-style: only provided fields are changed; omitted fields keep their current values. You can update: title, scheduleHour, notification channels, email recipients, WhatsApp settings, alertEmail, sourceIds, comparisonPeriod. NOTIFICATION CHANNELS: Pass notificationChannels to change how the report is delivered. Array of one or more: "email", "in-app", "whatsapp". When changing to include "email", make sure recipients are set (either already configured or passed in this call). When changing to include "whatsapp", make sure whatsappUrl is set. CRITICAL PARAMS — ASK WHEN AMBIGUOUS: - When the user says "change the email", ask whether they mean: alert email (failure alerts), recipient list (who receives the report), or both. Then pass only the relevant parameter(s). - alertEmail accepts ONLY ONE email. If the user wants multiple, tell them only one is allowed. - When the user says "send via WhatsApp", you need the whatsappUrl. If not provided, ask. WHEN TO CALL: Use when the user wants to modify an existing automation's settings. Examples: 'Change the automation time to 10am', 'Add another recipient', 'Update the alert email to X', 'Switch to WhatsApp delivery', 'Add in-app notifications', 'Change who receives the report'. PREREQUISITES: Call list_automations or get_automation first to get the automation id and current values.
update_goal
ChatGPTUpdate an existing KPI goal's target value and/or alert configuration. When targetValue is provided, creates a new goal period with the updated target starting from the current period boundaries. Alert settings can be toggled independently. CRITICAL PARAMS — ASK WHEN AMBIGUOUS: - If the user says "change the goal" without specifying a new target number, ask: "What should the new target value be?" WHEN TO CALL: Use when the user wants to modify an existing goal's target or alerts. Examples: 'Increase my Instagram follower goal to 15000', 'Change the target for my ads conversion goal', 'Update the KPI target', 'Enable alerts when the goal is reached'. PREREQUISITES: Call list_goals first to find the tracked_metric_id.
update_timeline_event
ChatGPTPartially update an existing timeline event. PATCH-style: only provided fields are changed; omitted fields keep their current values. Never pass an empty string for content. CONTENT FORMATTING RULES (when updating content): The same HTML formatting rules from create_timeline_event apply here. When the user asks to update or improve event content, ALWAYS produce well-structured HTML: - Use <b> or <strong> for section headings and key terms - Use <ul>/<li> for bullet-point lists and <ol>/<li> for ordered/ranked items - Use <br> for line breaks between sections - Organize into logical sections (Summary, Analysis, Strengths, Weaknesses, Recommendations, etc.) - If the existing content is unstructured plain text and the user asks for any edit, take the opportunity to restructure the entire content into proper HTML format. Never produce a plain wall of text for analytical or descriptive events. WHEN TO CALL: Use when the user wants to modify an existing timeline event. Examples: 'Change the date of milestone X', 'Update the campaign launch note', 'Move this event to a different project', 'Link this timeline event to a report', 'Improve the formatting of this event'. PREREQUISITES: Call list_timeline_events or get_timeline_event first to find the event ID.
update_webhook
ChatGPTUpdate an existing webhook subscription by ID. PATCH-style: only provided fields are changed; omitted fields keep their current values. You can change the callback URL, event type, or project scope. Use clearProjectScope to make the webhook receive events for all projects. Valid event types: report_viewed, report_created, dashboard_created, automation_executed, control_goal_met, control_goal_not_met, timeline_milestone_added. PROJECT SCOPE: Company-wide webhooks (no project_id) can only be modified by users who reach every project in the company. The same applies to clearProjectScope, which turns a project webhook into a company-wide one. WHEN TO CALL: Use when the user wants to modify an existing webhook's settings. Examples: 'Change webhook 123 URL to https://new.example.com/hook', 'Update webhook to listen for automation_executed', 'Scope webhook to project 5'. PREREQUISITES: Call list_webhooks first to get the webhook id.