KEYWORDS: utm, utms, utm_source, utm_medium, utm_campaign, utm_term, utm_content, tracking parameters, search utm, find utm, placeholder, UPDATE ME, audit

            USE THIS TOOL WHEN THE USER ASKS:
            - "Which campaigns still have UPDATE ME in their UTMs?"
            - "Which campaigns tag utm_source as <something>?"
            - Any audit of UTM VALUES across campaigns.

            CRITICAL - DO NOT ANSWER THIS FROM CAMPAIGN NAMES. Campaign names, experiment
            names and tags do not contain UTM values. Searching them returns nothing and
            produces a confident WRONG "no campaigns found" - the exact failure this tool
            was built to end. If this tool errors or is unavailable, say you cannot check
            rather than falling back to a name search.

            INHERITANCE RULE - READ BEFORE ANSWERING ANY UTM QUESTION:
            UTMs are inherited, never blank. A campaign channel with an empty stored
            mapping does NOT have "no UTMs" - it tracks with the account's UTM defaults,
            and where the account set nothing it tracks with the Metadata platform default.
            Roughly half of all channel rows in production are in that inherited state.
            NEVER report "no UTMs configured" from an empty stored field: report the
            resolved value and its origin.

            ORIGIN IS PER CHANNEL, not per key: a channel with an empty stored mapping
            inherits the account default whole, so a channel whose resolved mapping differs
            at all from that is stored on the campaign and every one of its values is an
            override. The per-key `same_as_default` flag says whether that one key happens
            to match the default anyway.

            ORIGIN VALUES:
            - campaign_override: stored on this campaign channel, differs from what it would inherit.
            - account_default: inherited from this account's UTM defaults.
            - platform_default: inherited from the Metadata-wide default (account set nothing).
            - not_set: the channel really has no UTM mapping (non-sponsored channels only).

            HONEST LIMIT: a campaign that stores a mapping identical to the default it
            would inherit is reported as inherited. The platform returns resolved values
            with no provenance, so that case cannot be distinguished - say so rather than
            claiming the campaign has no override.

            The match is a case-insensitive SUBSTRING over each enabled channel's EFFECTIVE
            (post-inheritance) UTM value, so a campaign that inherits a matching account
            default is returned too - which is correct, that is what it actually tracks with.
            It matches VALUES, not keys: searching "utm_source" finds nothing.

            MINIMUM 3 CHARACTERS. A shorter value is refused rather than sent, because the
            platform ignores a sub-minimum filter and would return the whole campaign list,
            which reads as "everything matches".

            Optional filters mirror list_wizard_campaigns: page, size, sort_by, sort_order,
            status (Draft, Launched, Finished), experiment_statuses, visibility, name.

            RESPONSE SHAPE: same as list_wizard_campaigns -
            {"totalElements": 20, "totalPages": 1, "data": [{"id": 173290, "name": "...", "status": "Launched", ...}]}

            The rows do NOT include the matching UTM value. To show WHICH parameter matched,
            call get_campaign_utms on the campaigns returned.

            Page through until the returned rows cover totalElements before reporting a count.

            READ-ONLY, current account only.