Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

android_to_ios_app_mapping_details__get

Read-onlyIdempotent

Fetch a specific Android-to-iOS app mapping detail using its ID to access package name and SHA-256 certificate fingerprints.

Instructions

Read one android to iOS app mapping detail by ID. [GET /v1/androidToIosAppMappingDetails/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
fields_androidToIosAppMappingDetailsNothe fields to include for returned resources of type androidToIosAppMappingDetails 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.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / fields_androidToIosAppMappingDetails
      Added value: +{
+  "description": "the fields to include for returned resources of type androidToIosAppMappingDetails Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "packageName",
+      "appSigningKeyPublicCertificateSha256Fingerprints"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
  3. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description simply says 'Read,' which is consistent but adds no additional behavioral context like return size, pagination, or permission requirements. The size warning appears in the schema parameter description, not the tool description.

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 concise sentence that front-loads the action and resource, and includes the HTTP endpoint for clarity. No unnecessary words.

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?

With readOnly/idempotent annotations and a fully described schema, the tool is adequately specified for a simple get-by-ID operation. The description is minimal but sufficient, and the ID parameter's reference to the list call helps complete the context. No output schema is present, but none is needed for a read operation.

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 coverage is 100% with both parameters clearly described: id as 'ID from the matching list call' and fields as selectable attributes with a note about the 200 KB row size. The tool description itself adds no parameter meaning, relying fully on the schema, which meets the baseline for high coverage.

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 'Read one android to iOS app mapping detail by ID,' which clearly identifies the action (read) and resource (android-to-iOS mapping detail). This differentiates it from sibling tools like the create/update/delete variants and the list tool, which serve different purposes. The endpoint path reinforces the scope.

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 implies usage via 'by ID' but does not explicitly mention alternatives or when-not-to-use. The schema's id parameter description 'ID from the matching list call' provides some context, but the description itself lacks explicit guidance on choosing this tool over the list or other mapping tools.

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