Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__app_price_points__list

Read-onlyIdempotent

List permitted price points for an app, filter by territory to locate the matching price point ID for setting a purchase price.

Instructions

List the allowed price points for an app's purchase price. Filter by territory (country) to find the price point ID matching the price you want to set. [GET /v1/apps/{id}/appPricePoints]

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_territoryNofilter by id(s) of related 'territory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: "US" is accepted and silently returns an empty list.
fields_appPricePointsNothe fields to include for returned resources of type appPricePoints 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.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. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / fields_appPricePoints
      Added value: +{
+  "description": "the fields to include for returned resources of type appPricePoints Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "customerPrice",
+      "proceeds",
+      "app",
+      "equalizations",
+      "territory"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / filter_territory / description
      Previous value: -"filter by id(s) of related 'territory'"New value: +"filter by id(s) of related 'territory' Three-letter ISO-3166 alpha-3 code — USA, TUR, DEU, GBR. Not the two-letter form: \"US\" is accepted and silently returns an empty list."
    • 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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that this is a lookup used for future price-setting, but does not disclose additional behavior such as pagination limits or silent empty-result behavior. No contradiction with 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?

Two sentences plus an endpoint reference with no filler. The primary purpose is front-loaded, followed by a practical use case, making it easy for an agent to parse quickly.

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 description is complete enough for a list operation: it states what is listed, how to narrow it, and the purpose of the result. With no output schema, a slightly more explicit statement of the response shape would help, but 'find the price point ID' reasonably implies the output.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that filter_territory is how you locate a price point ID for a target price, which enriches the otherwise generic schema parameter descriptions.

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') and a specific resource ('allowed price points for an app's purchase price'), plus the exact endpoint. It clearly distinguishes this from siblings like pricing__set_subscription_price or apps__app_price_schedule__get by focusing on retrieving price-point IDs.

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

Usage Guidelines4/5

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

The description gives practical guidance: filter by territory to find the price point ID matching the price you want to set. It does not explicitly name alternatives or when-not-to-use cases, which prevents a 5, but the intended use is clear.

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