Wingz by Wingify

Delete one rule from a feature in an environment. Before calling: List rules with ``fe_list_feature_flag_rules_tool`` to confirm ``rule_id_or_key``. Returns: Markdown confirmation and any delete payload returned by the API. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_delete_feature_flag_rule_tool

Return every variation preview URL in backend order. Includes control and disabled variations. Maps each URL to its variation id from ``_vis_preview_data``. Does not take screenshots. [AGENT INSTRUCTIONS] Call after a successful campaign save in chat mode to obtain Wingify preview links. The first returned variation URL is the default button target; verification should inspect the intended saved variation. Returns: dict: campaign_id and variations [{variation_id, preview_url}] in backend order. Raises: ValueError: If the campaign is not found or preview URLs cannot be fetched. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

get_campaign_preview_urls_tool

Fetch one feature flag by numeric id or string key (full config: variables with ids, variations, goals, rules count). Before calling: Use ``fe_list_feature_flags_tool`` if you do not know the id/key. Use the response when: Updating variables or variations (you need server ``id`` values). Building rule payloads that reference ``featureVariationId``. Returns: Markdown summary. If the flag does not exist or the API returns no ``_data``, the output explains empty payload rather than failing silently. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_get_feature_flag_tool

Fetch a single rule by rule id or key under a feature and environment. Before calling: Use ``fe_list_feature_flag_rules_tool`` to discover ``rule_id_or_key``. Returns: Markdown rule detail. If the rule does not exist or ``_data`` is empty, the tool explains missing payload instead of assuming fields. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_get_feature_flag_rule_tool

Generate a preview URL for a campaign variation. Uses the campaign editor URL from campaign data, checks that VWO SmartCode is installed on that page, then fetches the variation preview URL. [AGENT INSTRUCTIONS] Call this when you want to preview the changes you made to a variation, typically after calling something like update_campaign_config. Do not use this for campaign reports. If SmartCode is not installed, tell the user the preview cannot apply changes and share the returned message. Otherwise return the preview_url so they can open it. Note: The preview URL needs a browser environment for the changes to be visible - open it in your browser. Returns: dict: ``smartcode_installed`` and either ``preview_url`` or ``message``. Raises: ValueError: If SmartCode analysis fails, the editor URL cannot be resolved from campaign data, or the preview-urls request fails.

get_variation_preview_url

Fetch account-level configuration, SmartCode properties, and product subscription details for the authenticated Wingify account. [AGENT INSTRUCTIONS] Call this tool at the start of any workflow that requires knowing the account's active products, plan types, or SmartCode setup — before calling product-specific tools. Display the returned markdown exactly as returned; do not reformat or summarise it. Use the data here to answer questions about account setup, tracking, integrations, and enabled features without making additional API calls. Returns: str: Markdown report including: - Account ID, name, settings, and hierarchy - Enabled products (Testing, Insights, Engage, Deploy, Data360, etc.) and plan types - SmartCode properties table (domains, installation status, platform types, last activity) - Integration settings (GA, GTM, UA, etc.) Display directly — do not wrap in conversational text or reformat. Raises: ValueError: If authentication fails or the account API request fails. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

get_account_details_tool

Fetch day-by-day conversion data for a Wingify campaign to surface trends over time. [AGENT INSTRUCTIONS] Use this tool only when the user asks about trends, patterns over time, or day-over-day performance — not for a single-point performance snapshot (use fetch_campaign_report_tool for that). Returns: str: Markdown report with daily conversion rates per variation. Suitable for identifying ramp-up periods, seasonality, or sudden performance shifts. Raises: ValueError: If campaign_id is invalid or not found. Verify the ID using get_campaigns_overview_tool and retry. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fetch_campaign_daywise_data_report_tool

Retrieve the raw code injected via Wingify's visual editor for each variation. Extracts the editorData stack — the sequence of CSS/JS snippets written directly inside VWO's editor — and returns them as fenced code blocks, one section per variation. [AGENT INSTRUCTIONS] Call this tool ONLY when the user explicitly needs the raw editor code itself — to inspect it, copy it, or reuse it in a new campaign. Do NOT call this for campaign summaries, understanding what a variation does, comparing variation changes, or QA analysis. Use fetch_campaign_report_tool for all of those. Returns: str: Markdown with the campaign name as a heading and each variation's injected editor code in fenced code blocks. Raises: ValueError: If the campaign is not found. Verify the ID with get_campaigns_overview_tool and retry. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

get_campaign_variation_code_tool

Fetch performance data for a Wingify campaign — conversion rates, lift, and goal results per variation. [AGENT INSTRUCTIONS] Use for point-in-time or segmented campaign performance — conversion rates, lift, chance to beat control, and goal IDs. Use fetch_campaign_daywise_data_report_tool instead when the user asks about trends or day-over-day patterns. Pass segment_description in plain language to scope by audience — resolution happens automatically. Date params use YYYY-MM-DD (unlike heatmap/recording tools which use DD/MM/YYYY). Returns: str: Markdown report containing per-variation results — conversion rate, lift over control, chance to beat control, goal IDs, and statistical status. Raises: ValueError: If campaign_id is invalid or not found. Verify the ID using get_campaigns_overview_tool and retry. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fetch_campaign_report_tool

List Wingify campaigns matching the given filters, returning a formatted overview table. [AGENT INSTRUCTIONS] DISPLAY the returned markdown table exactly as-is — do not reformat, summarize, or condense it. Always prefix the response with: "Here are the campaigns for the period [start_time] to [end_time]:" When resolving a campaign name to an ID, extract the matched campaign_id silently and pass it to the next capability without asking the user to confirm. Returns: str: Complete markdown with a summary table. Contains campaign IDs, names, statuses, types, and basic metrics. Display this output directly without modification. Raises: ValueError: If an invalid status value is provided. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

get_campaigns_overview_tool

List account-wide Data360 metrics usable with feature flags (API filter: flag-testing campaign type). Call this before: ``fe_create_feature_flag_tool`` / ``fe_update_feature_flag_tool`` / ``fe_create_feature_flag_with_defaults_tool`` when you need valid ``metricName`` values for goals. Returns: Markdown table of metrics. An empty list means no metrics matched the filter—not necessarily an auth error; verify account setup and metric catalog. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_get_fme_metrics_tool

Get available Wingify Data360 metrics for the authenticated account. [AGENT INSTRUCTIONS] ALWAYS call this tool before create_split_url_campaign or create_ab_campaign to discover available metric IDs. Never guess or hardcode metric values — use the IDs returned here as inputs to the campaign creation tools. Returns: dict: {"Available Metrics": <list of metric objects>} where each metric object includes the metric ID, name, and type. Pass these IDs when creating campaigns. Raises: ValueError: If the Data360 metrics fetch fails. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

get_data360_entities

List FME projects and their environments (ids, names, enabled flags, rule counts where available). Call this first when: Any tool requires ``environment_id_or_key`` and you are unsure of ids or standard env names (e.g. Dev/Staging/Prod mappings differ by account). Returns: Markdown tables for projects and environments. Sensitive fields like sdk keys are not surfaced in the primary tables. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_list_projects_and_environments_tool

List rules for a given feature in a given environment (paginated). Before calling: Resolve ``environment_id_or_key`` via ``fe_list_projects_and_environments_tool``. Resolve ``feature_id_or_key`` via ``fe_list_feature_flags_tool`` or ``fe_get_feature_flag_tool``. Returns: Markdown list/table. An empty rule set is a valid outcome—check offset/limit and that rules were created for that env/feature. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_list_feature_flag_rules_tool

List feature flags with pagination (limit/offset). Use this to: Discover ``feature_id_or_key`` values for get/update/delete/toggle. See counts and types before deeper calls. Empty page: A valid response may contain no rows; that is not an error—adjust ``offset`` or confirm the account has flags. Returns: Markdown table (and optional metadata block). [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_list_feature_flags_tool

Enable or disable a feature flag for one environment. Does not enable or disable individual rules — use ``fe_toggle_feature_flag_rules_tool`` for per-rule control. Before calling: Use ``fe_list_projects_and_environments_tool`` to resolve ``environment_id_or_key`` (numeric id or environment name/key as supported by your account). Use ``fe_list_feature_flags_tool`` to resolve ``feature_id_or_key``. Returns: Markdown summary of toggle result; empty API ``_data`` is handled gracefully. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_toggle_feature_flag_tool

Enable or disable one, many, or all rules for a feature in an environment. Behavior: If ``rule_ids`` is omitted (``None``), **all** rules for that feature in that environment are toggled. Pass one or more numeric ids to limit scope. An empty list (``[]``) is rejected — do not pass ``[]``. Enable only specific rule(s) (e.g. one rollout while others stay off): 1. ``fe_list_feature_flag_rules_tool`` — copy numeric ``id`` (not ``key``). 2. This tool with ``is_enabled=False`` and no ``rule_ids`` (disable all). 3. This tool with ``is_enabled=True`` and ``rule_ids=[<target_id>]``. Before calling: Confirm environment and feature ids/keys (projects list + feature list/get). Returns: Markdown summary of the toggle response. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_toggle_feature_flag_rules_tool

Patch an existing feature flag; only provided fields are sent to the API. Before calling: Call ``fe_get_feature_flag_tool`` for the same ``feature_id_or_key`` to obtain current variable ids, variation ids, and structure. For goals, ensure ``metricName`` values exist (``fe_get_fme_metrics_tool``). Notes: Omitting a field leaves it unchanged on the server (do not send empty lists unless you intend to clear something the API allows clearing). If the API returns an empty body after success, formatting still completes with a clear message. Returns: Markdown summary of the updated flag. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_update_feature_flag_tool

Update traffic or variation allocation for one rule (``campaign_data`` only; other rule fields unchanged unless API allows). Before calling: Use ``fe_get_feature_flag_rule_tool`` or list output to confirm ``rule_id_or_key`` and current ``campaignData`` shape. Variation ids in ``campaign_data`` must match the feature's variations from ``fe_get_feature_flag_tool``. Returns: Markdown summary of the updated rule. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

fe_update_feature_flag_rule_tool

Update the configuration of an existing Wingify campaign (URLs, variations, goals, schedule, or name). The control_url parameter is only applicable for split URL campaigns. To update the URLs for an A/B test, use the urls_to_include parameter. To update the name of the campaign, use the campaign_name parameter. If the user asks to update control URL/URLs for an **A/B test** campaign, use the urls_to_include parameter. If the user asks to update the URLs for a **split URL campaign**, use the control_url parameter. IMPORTANT: - This is a REPLACE operation. Include ALL items you want to keep. Items not included will be removed. If campaign_name is not provided, the campaign name will not be updated. *variations is a full replace list. Every variation you want to keep must appear with its id. Omitted ids are deleted. Updating JS on one variation still requires listing all other variations you want to keep unchanged (e.g. {"id": 1} for control).* - *Use fetch_campaign_report_tool first to get existing variation/goal IDs for the campaign.* - *Do not make changes to a campaign if it is RUNNING. You can ONLY make changes to campaigns that are not live.* Returns: Success message. Raises: ValueError: If the campaign is RUNNING, required IDs are missing, or the API call fails. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

update_campaign_config

Start or pause a Wingify campaign by updating its status. [AGENT INSTRUCTIONS] Use this tool when the user explicitly asks to start, resume, or pause a campaign. Always confirm the campaign ID with the user before changing its status. Verify the current status first using get_campaigns_overview_tool if uncertain. Returns: str: Confirmation message indicating the updated campaign status. Raises: ValueError: If campaign_id is invalid or the status transition is not allowed. [SUB_ACCOUNT_ACCESS] Optional `account_id`: run this tool against a specific Wingify sub-account instead of your main account. Must be your main account or one of its active sub-accounts — unauthorized IDs are rejected. Defaults to your main account when omitted. [/SUB_ACCOUNT_ACCESS]

update_campaign_status