logly/mureo

Name resolution across MCC hierarchies in list_accessible_accounts

Patch release on top of v0.9.10. One Google Ads adapter fix, backward-compatible.

Fixed — list_accessible_accounts resolves name + manager flag for customers outside the operator-default MCC

mureo.google_ads.list_accessible_accounts (made public in v0.9.10) queried every customer returned by listAccessibleCustomers through the operator-wide credentials.login_customer_id. The Google Ads API rejects a request when the customer_id is not reachable via the request's login_customer_id header, so customers reached only through a manager-link to a different MCC silently fell back to the raw ID for name and False for is_manager — and their child accounts were never traversed.

The fix builds a fresh client per customer with the customer's own ID as login_customer_id for both the info query and the child traversal. The operator-default base_client is now used only for listAccessibleCustomers itself. The function's signature and list[dict[str, Any]] return shape are unchanged.

PRs in this release

• #147 — fix(google-ads): resolve name + manager flag for customers outside operator-default MCC

Upgrade

pip install --upgrade mureo

No code changes required for callers. Pickers built on list_accessible_accounts automatically surface descriptive names and manager flags for separately-linked MCCs on the next call.