Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__app_events__list

Read-onlyIdempotent

Retrieve app events for a specific app by name, bundle ID, or Apple ID. Filter by event state and include localizations to manage promotional event schedules.

Instructions

List the app events belonging to an app. [GET /v1/apps/{id}/appEvents]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
limitNomaximum resources per page
includeNocomma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned.
next_urlNoAbsolute links.next URL from a previous response.
filter_idNofilter by id(s)
fields_appEventsNothe fields to include for returned resources of type appEvents Return only these attributes. A full row set can exceed 200 KB.
filter_eventStateNofilter by attribute 'eventState'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / id / description
      Previous value: -"ID from the matching list call."New value: +"App name, bundle ID (com.example.app) or numeric Apple ID."
  2. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  3. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appEvents
      Added value: +{
+  "description": "the fields to include for returned resources of type appEvents Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "referenceName",
+      "badge",
+      "eventState",
+      "deepLink",
+      "purchaseRequirement",
+      "primaryLocale",
+      "priority",
+      "purpose",
+      "territorySchedules",
+      "archivedTerritorySchedules",
+      "localizations"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • changedInput schema / properties / include / description
      Previous value: -"comma-separated list of relationships to include"New value: +"comma-separated list of relationships to include Pull related records in the same call. Without it, checking a relationship costs one extra call per row returned."
    • changedInput schema / properties / next_url / description
      Previous value: -"Absolute `links.next` URL from a previous response, to fetch the next page. When set, all other parameters are ignored."New value: +"Absolute links.next URL from a previous response."
  4. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's safety burden is light and it does not contradict them. It adds the endpoint path and confirms the operation is a scoped read of events for a single app. No additional behavioral traits (pagination defaults, auth requirements) are disclosed, which is acceptable given the annotations.

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

Conciseness5/5

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

The entire description is two short sentences with no filler—the verb/resource statement is front-loaded, and the REST endpoint is a compact second sentence. Nothing could be trimmed without losing information.

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

Completeness3/5

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

For a read-only list endpoint with annotations covering safety and a schema documenting every parameter, the minimal description is nearly adequate. However, there is no output schema and the description does not characterize the return shape or pagination behavior beyond the schema's 'limit' hint, leaving modest gaps for an agent to resolve.

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?

Schema description coverage is 100%—all seven parameters have individual descriptions, including helpful details like 'A full row set can exceed 200 KB' and the relationship-cost note on include. The tool description itself adds no parameter-level detail, but per the rubric, high schema coverage sets the baseline at 3.

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

Purpose5/5

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

The description states a specific verb ('List'), a distinct resource ('app events'), and the scoping relationship ('belonging to an app'), and appends the exact REST endpoint [GET /v1/apps/{id}/appEvents]. No sibling tool targets app events, so the resource is unambiguous.

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

Usage Guidelines2/5

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

No guidance is given about when to choose this tool over alternatives, and no alternatives or exclusions are named. Context signals show a large sibling suite (~250 tools), so an agent must infer usage mostly from the name. The schema's include-parameter note ('one extra call per row returned') is the only usage hint, and it lives at parameter level rather than tool level.

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

Deploy Server

Other Tools