Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

beta_license_agreements__list

Read-onlyIdempotent

List beta license agreements from App Store Connect. Filter by app ID or include related app records to get agreement text and app details in one call.

Instructions

List beta license agreements. [GET /v1/betaLicenseAgreements]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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_appNofilter by id(s) of related 'app' The numeric Apple ID from apps__list, not the bundle ID. A bundle ID matches nothing and comes back as 200 with an empty list.
fields_betaLicenseAgreementsNothe fields to include for returned resources of type betaLicenseAgreements Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • changedInput schema / properties / filter_app / description
      Previous value: -"filter by id(s) of related 'app'"New value: +"filter by id(s) of related 'app' The numeric Apple ID from apps__list, not the bundle ID. A bundle ID matches nothing and comes back as 200 with an empty list."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_betaLicenseAgreements
      Added value: +{
+  "description": "the fields to include for returned resources of type betaLicenseAgreements Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "agreementText",
+      "app"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • 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."
  3. First observedv1.3.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond the endpoint URL, such as pagination behavior, rate limits, or response structure. The added value over annotations is minimal.

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

Conciseness3/5

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

The description is extremely concise, consisting of one sentence plus the endpoint. It front-loads the purpose efficiently. However, it is too brief to be fully informative; a second sentence about typical use or output format would improve it without adding much length.

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

Completeness2/5

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

Given the tool has 5 parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain the return format, how to paginate using 'next_url', or what relationship inclusion ('include') does. The description also fails to differentiate this list from the similar 'apps__beta_license_agreement__get' endpoint.

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%, and the schema descriptions are detailed (e.g., filter_app specifies valid ID format). The tool description does not add any parameter explanations beyond what is already in the schema. With high coverage, a baseline of 3 is appropriate; the description neither improves nor detracts.

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 clearly states 'List beta license agreements' with a verb and resource. It distinguishes from similar tools like 'beta_license_agreements__get' (single item retrieval) and 'beta_license_agreements__update' (modification) through the use of 'list'. However, it does not elaborate on what a beta license agreement is or how it differs from related list endpoints like 'apps__beta_license_agreement__get'.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'beta_license_agreements__get' for a single record, 'apps__beta_license_agreement__get' for a specific app's agreement, or other list tools. There is no mention of prerequisites, typical use cases, or 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