/**
 * Google Analytics Admin API (GA4) — read-only MCP tools.
 *
 * These tools wrap the googleapis `analyticsadmin` v1beta client and expose ONLY
 * list/get methods. There are deliberately no create/update/delete tools and no
 * `confirm` gate, because nothing here mutates GA4 state. They power the senior
 * audit framework's GA4_ADMIN checks: custom dimensions/metrics, data streams &
 * measurement IDs, data retention, enhanced measurement, conversion/key events,
 * and Google Ads links.
 *
 * AUTH: Requires the `https://www.googleapis.com/auth/analytics.readonly` scope
 * to be present on the active credentials (see ALL_SCOPES in auth/googleAuth).
 * If that scope is missing, Google returns a 403 and the tools surface a clear
 * hint to re-run `npm run auth:google`.
 *
 * LIMITATIONS (not exposed by the GA4 Admin API v1beta and therefore NOT faked):
 *   - Internal traffic / unwanted-referral *data filters*: the Admin API has no
 *     public "dataFilters" collection. Internal-traffic and developer-traffic
 *     filtering is configured per data stream and is not separately listable.
 *   - Referral exclusions / "list unwanted referrals": no dedicated Admin API
 *     resource. (Referral configuration lives inside data stream settings.)
 *   - Channel groups and audiences exist only on the v1alpha surface; they are
 *     intentionally omitted from this read-only v1beta tool set.
 * These gaps are documented rather than stubbed so the audit never reports a
 * false signal.
 */
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import type { Ga4AdminClient, Ga4AdminAlphaClient } from '../utils/ga4Client.js';
export declare function registerGa4AdminTools(server: McpServer, getClient: () => Ga4AdminClient, getAlphaClient: () => Ga4AdminAlphaClient): void;
//# sourceMappingURL=ga4Admin.d.ts.map