sonar

App Engagement (App Store Connect)

sonar_app_engagement

Read-onlyIdempotent

App Store Connect App Analytics for one of your own iOS apps: the impressions → product page views → downloads funnel with conversion rates (page_view_rate, download_rate) and App Store search share, impressions by source (App Store search, browse, app referrer, web referrer…), plus daily installs, deletions and sessions. Impressions follow App Store Connect's definition and INCLUDE product page views, so totals reconcile with ASC. Downloads come from the Sales report. Same numbers as the Engagement page. iOS only. Requires the Indie or Agency plan AND an App Store Connect connection with an Admin-role key (key_lacks_analytics otherwise); Apple delivers the first analytics 24-48 hours after connecting (pending). Always check status: anything other than ready (not_connected, not_ios, app_not_in_account, pending, key_lacks_analytics) means there's no data and message says how to fix it — never read an empty series as zero. Days Apple hasn't reported yet have reported: false and null metrics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "sonar_app_engagement"
  }
}

Input Schema

Name	Required	Description
`end`	No	Last day of the window (YYYY-MM-DD, inclusive). Default yesterday (UTC) — Apple posts a day the next morning at the earliest.
`days`	No	Window length in days (1-366) when `start` is omitted. Default 30.
`start`	No	First day of the window (YYYY-MM-DD, inclusive). Omit to count `days` back from `end`.
`store`	No	Only needed when `app_id` is a store id tracked in both stores. App Store Connect data is iOS-only.
`app_id`	Yes	Sonar app UUID of one of your own tracked iOS apps — the `id` returned by sonar_list_apps or sonar_create_product. The app's store id (bundle id) also works; pass `store` if it exists in both stores.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses important behavioral details: impressions include product page views, downloads come from the Sales report, Apple data can take 24-48 hours, statuses such as not_connected/pending/key_lacks_analytics mean no data, and unreported days have reported:false with null metrics. It also warns never to read an empty series as zero, which is exactly the kind of operational context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose and key metrics, and almost every sentence earns its place by adding scope, caveats, or status behavior. It is dense and presented as one long paragraph, which makes it slightly harder to scan, but it avoids filler and repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the burden of explaining what comes back, and it does: funnel metrics, conversion rates, search share, impressions by source, installs, deletions, sessions, status semantics, and null/reported behavior. Given the tool's complexity and external data dependencies, the definition is complete enough for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3 when the description adds little parameter-specific meaning. The description reinforces that the tool is for one of the user's own iOS apps and mentions iOS-only scope, but it does not add syntax or usage detail for start, end, days, store, or app_id beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: App Store Connect App Analytics for one of the user's own iOS apps, including the impressions-to-downloads funnel, conversion rates, search share, and installs/deletions/sessions. It is clear what the tool does, but it does not explicitly name or contrast sibling tools such as sonar_app_sales or sonar_app_overview, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides useful context and prerequisites: iOS only, Indie or Agency plan required, Admin-role App Store Connect key required, and the need to check status before reading data. However, it does not explicitly say when to use this tool instead of sibling tools like sonar_app_sales, sonar_app_revenue, or sonar_app_overview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All sonar tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.