Update to Google Analytics | LoomaScale

{
  "description": "Analyze the user's connected Google Analytics 4 (GA4) properties with LoomaScale. Use for property discovery, website traffic, engagement, landing pages, events, key events, revenue, realtime activity, funnels and conversion attribution reports. Reports are read-only; eligible configuration-preview accounts can request supported settings changes. Do not invoke for general analytics definitions, installing tracking or changing ad campaigns.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 539
    },
    {
      "relative_path": "references/reporting.md",
      "size_in_bytes": 4380
    }
  ],
  "name": "loomascale-ga4",
  "skill_md_contents": "---\nname: loomascale-ga4\ndescription: Analyze the user's connected Google Analytics 4 (GA4) properties with LoomaScale. Use for property discovery, website traffic, engagement, landing pages, events, key events, revenue, realtime activity, funnels and conversion attribution reports. Reports are read-only; eligible configuration-preview accounts can request supported settings changes. Do not invoke for general analytics definitions, installing tracking or changing ad campaigns.\n---\n\n# Google Analytics 4 reporting with LoomaScale\n\nUse the user's connected Google Analytics 4 properties to answer a reporting\nquestion with account evidence. This package connects to\n`https://api.loomascale.com/mcp/ga4`. Reporting reads Analytics data and settings.\nEligible configuration-preview accounts may also have settings tools; follow\nthe configuration rules below. This package cannot install tracking or edit\ncampaigns, and it never deletes a property or stream.\n\n## Resolve the property and reporting context\n\nReuse an already verified property from the conversation. Otherwise call\n`ga4_get_account_summaries` to discover reachable accounts and properties. Use\n`property_id` as the listed number or `properties/<number>`; never substitute a\nGoogle Ads customer ID or a `G-...` measurement ID. Respect disabled properties.\nIf several properties fit and the task does not identify one, ask which to use.\n\nRead `ga4_get_property_details` for the property's time zone and currency before\ninterpreting historical dates or money. Honor the user's period. If none is given,\nuse the last 30 complete days in that time zone; add a preceding equal-length\ncomparison when investigating a change. State the exact dates. Realtime questions\nuse their own last-30-minute window instead.\n\nInspect available tool descriptions and input schemas. Names here are the\nserver's tool names; a client may add a namespace. Live schemas and access\npermissions determine supported inputs and reports.\n\n## Choose the report that answers the question\n\n| Question | Tool |\n| --- | --- |\n| Which GA4 accounts and properties can I access? | `ga4_get_account_summaries` |\n| What time zone and currency does this property use? | `ga4_get_property_details` |\n| Which sources, landing pages or devices bring traffic, key events or revenue? | `ga4_run_report` |\n| What activity or events appeared in the last 30 minutes? | `ga4_run_realtime_report` |\n| Where do users leave an ordered series of events? | `ga4_run_funnel_report` |\n| What conversions, cost or ROAS does GA4 attribute? | `ga4_run_conversions_report` |\n| What custom dimensions and metrics are registered? | `ga4_get_custom_dimensions_and_metrics` |\n| What dated property annotations might explain a change? | `ga4_list_property_annotations` |\n| Which Google Ads accounts are already linked? | `ga4_list_google_ads_links` |\n\nRead [report inputs and limitations](references/reporting.md) for report shapes,\npagination, realtime compatibility, funnel steps and attribution. For a diagnosis\nof changing results or a prioritized interpretation, use\n[GA4 insights](../ga4-insights/SKILL.md).\n\n## Handle an explicitly requested configuration change\n\nKeep reporting read-only. Never change settings as a side effect of an analysis.\nFor eligible configuration-preview accounts, available tools may manage key\nevents, event create and edit rules, enhanced measurement, data redaction, and\ncreate or update web streams. Event rules apply to future incoming events;\ncreating a rule does not emit an event immediately or rewrite historical data.\nCreating a stream does not install a website tag.\n\nUse only tools available to the connected account and their live schemas.\nBefore a write, show the exact property, stream or rule and proposed changes\nusing `dry_run=true`, then obtain the user's approval of those changes. Apply\nonly the approved change and report the verified result. If the preview tool or\nrequired permission is unavailable, explain the limitation and direct the user\nto the relevant Google Analytics setting instead.\n\n## Handle access and helper tools accurately\n\n- If authorization is missing or expired, use the connection link returned by the\n  tool or the [LoomaScale connections dashboard](https://loomascale.com/dashboard/connections).\n  A missing property can reflect the Google login's permissions or a disabled\n  property; an empty report is not proof that tracking is absent.\n- For a usage-limit refusal, call `loomascale_check_quota` once and explain the\n  allowance or reset it actually reports. A usage allowance is not an ad budget.\n- `loomascale_request_feature` sends a message to the LoomaScale team. Call it\n  only when the user asks to send a feature request; a reporting question does\n  not authorize sending a message. Do not claim every helper is read-only.\n- For an invalid report, use the returned error and current schema to correct a\n  supported input. Explain remaining permission, API or data limitations instead\n  of repeatedly retrying the same refusal or inventing zero results.\n\n## Return a result the user can assess\n\nGive the answer, property, exact dates, time zone and currency where relevant.\nKeep observed results separate from hypotheses. Include material sampling,\nthresholding, pagination and attribution limits returned by the API. Recommend\nspecific next steps for configuration changes. Claim a settings change only\nafter an approved write succeeds; do not claim to have verified live tag firing.\n"
}