KEYWORDS: utm, utms, utm_source, utm_medium, utm_campaign, utm_term, utm_content, tracking parameters, final url suffix, placeholder, UPDATE ME, inherited, account default, campaign override

            USE THIS TOOL WHEN THE USER ASKS:
            - "What UTMs does campaign X use?" / "Show me the tracking parameters on this campaign"
            - "Does this campaign override the account UTM defaults?"
            - "Does campaign X still have the UPDATE ME placeholder in its UTMs?"

            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.

            INPUT: campaign_id - the WIZARD campaign id (the `id` field returned by
            list_wizard_campaigns / search_campaigns_by_names). Not an experiment id.

            RESPONSE SHAPE:
            {
              "campaign_id": 173290,
              "is_editable": true,
              "channels": {
                "LINKEDIN": {
                  "origin": "campaign_override",
                  "inherited_from": "account_default",
                  "values": {
                    "UTM_SOURCE": {"value": "UPDATE ME", "origin": "campaign_override", "same_as_default": false, "placeholder": true},
                    "UTM_MEDIUM": {"value": "AD_CHANNEL", "origin": "campaign_override", "same_as_default": true, "placeholder": false}
                  }
                }
              },
              "account_defaults": {"LINKEDIN": {"UTM_SOURCE": "Metadata", ...}, ...},
              "platform_default": {"UTM_SOURCE": "Metadata", "UTM_MEDIUM": "AD_CHANNEL", ...},
              "notes": ["..."]
            }

            `placeholder: true` marks a value that still carries the UPDATE ME placeholder -
            that is a real tracking defect worth reporting to the user.

            Values like AD_CHANNEL / OFFER_TYPE / AD_NAME are dynamic tokens the platform
            substitutes at serve time, not literal text.

            `platform_default` is a constant mirrored in mcp-server from the platform source;
            it is not fetched from an endpoint and covers sponsored channels only.

            READ-ONLY. To change a campaign channel's UTMs use set_campaign_utms; the
            account defaults are edited in the Metadata UI.