Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

apps__accessibility_declarations__list

Read-onlyIdempotent

List accessibility declarations for an app by ID, filter by state or device family, and select fields to return.

Instructions

List the accessibility declarations belonging to an app. [GET /v1/apps/{id}/accessibilityDeclarations]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesApp name, bundle ID (com.example.app) or numeric Apple ID.
limitNomaximum resources per page
next_urlNoAbsolute links.next URL from a previous response.
filter_stateNofilter by attribute 'state'
filter_deviceFamilyNofilter by attribute 'deviceFamily'
fields_accessibilityDeclarationsNothe fields to include for returned resources of type accessibilityDeclarations 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. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / fields_accessibilityDeclarations
      Added value: +{
+  "description": "the fields to include for returned resources of type accessibilityDeclarations Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "deviceFamily",
+      "state",
+      "supportsAudioDescriptions",
+      "supportsCaptions",
+      "supportsDarkInterface",
+      "supportsDifferentiateWithoutColorAlone",
+      "supportsLargerText",
+      "supportsReducedMotion",
+      "supportsSufficientContrast",
+      "supportsVoiceControl",
+      "supportsVoiceover"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
    • 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

B3.3/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, so the safety profile is fully covered. The description adds minimal behavioral context beyond confirming this is a GET scoped to an app; it does not disclose pagination behavior or the large-response concern hinted at in the schema. 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?

A single sentence that states the purpose and the endpoint with zero filler. The endpoint reference is immediately useful for confirming the operation shape, and every word earns its place.

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 tool with strong annotations and a fully documented schema, the description is adequate but thin. It omits the pagination behavior (limit/next_url), the filtering options (filter_state, filter_deviceFamily), and the 200 KB payload warning present in the schema, all of which would help an agent invoke it efficiently on large result sets.

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%, so all six parameters (id, limit, next_url, filter_state, filter_deviceFamily, fields_accessibilityDeclarations) are already documented in the schema. The description adds no parameter-specific meaning, making the baseline 3 appropriate.

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?

States a clear verb+resource ('List ... accessibility declarations') and scopes it to a specific app, reinforced by the endpoint '[GET /v1/apps/{id}/accessibilityDeclarations]'. It is obviously the list counterpart to the accessibility_declarations__create/get/update/delete siblings. However, it doesn't go beyond the name to explain what an accessibility declaration is, so it stops short of a 5.

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 on when to choose this list tool versus accessibility_declarations__get, or on when the filters should be used. The only usage signal is the embedded endpoint, which implies an app id is required. No exclusions, prerequisites, or alternative tools are mentioned.

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