What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

We need to retrieve MongoDB Atlas cluster-level tags when listing clusters via /api/atlas/v2/clusters. Today, the endpoint returns project tags but not cluster tags, so we must make additional API calls per cluster (or use other endpoints) to collect this metadata. This increases latency and complexity, and it does not scale well as the number of clusters grows.

What would you like to see happen?

Describe the desired outcome or enhancement.

Expose cluster tags directly in the cluster listing endpoint, ideally behind an optional flag to preserve current behavior, e.g. /api/atlas/v2/clusters?clustersTags=true. When enabled, each returned cluster should include its own tags (in addition to any existing project tag info), so clients can fetch clusters + their tags in a single request

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

This would significantly reduce the number of API calls we have to make to Atlas, improving overall performance and reliability of our workflows. Fewer calls means lower latency, simpler client logic, and a better user experience for internal tools that inventory or manage clusters across many projects/environments.

What steps, if any, are you taking today to manage this problem?

Today we work around this limitation by fetching clusters first, then making extra requests to retrieve tags for each cluster and merging the results client-side. We also try to cache results where possible, but we still incur a high number of calls and added complexity.