Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__build_uploads__list

Read-onlyIdempotent

List build uploads for an app using its name, bundle ID, or Apple ID. Filter by platform, state, or bundle version and sort results for quick access.

Instructions

List the build uploads belonging to an app. [GET /v1/apps/{id}/buildUploads]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
sortNocomma-separated list of sort expressions; resources will be sorted as specified
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_stateNofilter by state
filter_platformNofilter by attribute 'platform'
fields_buildUploadsNothe fields to include for returned resources of type buildUploads Return only these attributes. A full row set can exceed 200 KB.
filter_cfBundleVersionNofilter by attribute 'cfBundleVersion'
filter_cfBundleShortVersionStringNofilter by attribute 'cfBundleShortVersionString'

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_buildUploads
      Added value: +{
+  "description": "the fields to include for returned resources of type buildUploads Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "cfBundleShortVersionString",
+      "cfBundleVersion",
+      "createdDate",
+      "state",
+      "platform",
+      "uploadedDate",
+      "build",
+      "assetFile",
+      "assetDescriptionFile",
+      "assetSpiFile",
+      "buildUploadFiles"
+    ],
+    "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.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructtiveHint=false, and the description only repeats the read-only nature by saying 'List'. It adds no behavioral context beyond that, such as pagination behavior, filtering implications, relationship inclusion costs, or any side effects.

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 description is a single, focused sentence that immediately states the resource, scope, and underlying endpoint. No wasted words or redundant detail are present.

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

Completeness4/5

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

The concise description combined with the fully documented schema and read-only annotations provides enough operational context for an agent to invoke the tool correctly. The only minor gap is an explicit statement about response shape or pagination behavior, though the schema's next_url and limit parameters strongly imply it.

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?

With schema description coverage at 100%, the input schema already documents all ten parameters, including filters, sort, pagination, and field selection. The description contributes no additional parameter meaning, so the schema-heavy baseline of 3 is appropriate.

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 and resource: 'List the build uploads belonging to an app', and it reinforces the exact endpoint [GET /v1/apps/{id}/buildUploads]. This makes the operation distinguishable from 'get' siblings such as build_uploads__get and from apps__builds__list.

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?

The description gives a clear purpose, so an agent can infer when to call it: when build uploads for a particular app are needed. However, it provides no explicit guidance about when to prefer this over related tools like apps__builds__list or build_uploads__get, nor does it state any exclusions.

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