Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

alternative_distribution_package_variants_get_instance

Fetch one App Store Connect alternative distribution package variant by ID to inspect its download URL, expiration date, checksum, or key blob. Limit response fields as needed.

Instructions

GET /v1/alternativeDistributionPackageVariants/{id} (GET /v1/alternativeDistributionPackageVariants/{id})

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "alternative_distribution_package_variants_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_alternativeDistributionPackageVariantsNothe fields to include for returned resources of type alternativeDistributionPackageVariants

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description must carry the full behavioral burden, and it conveys nothing beyond the HTTP verb. It does not state whether the retrieval is read-only, what happens with an invalid id, whether fields filtering is required, or anything about the response shape.

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

Conciseness2/5

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

It is short, but the single sentence duplicates the same path twice in parentheses, which is pure waste rather than economy. There is no front-loaded purpose statement, just a raw endpoint string.

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

Completeness1/5

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

With no annotations, no output schema, and a terse path-only description, an agent has no information about the resource being fetched or what comes back. For a domain-specific resource like an alternative distribution package variant, this is far below the minimum needed to call it confidently.

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% — the 'id' and 'fields_alternativeDistributionPackageVariants' parameters are both documented in the schema, including the enum of selectable fields. The description adds zero meaning beyond it, so the baseline 3 for fully-covered schemas applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the tool name and its URL path ('GET /v1/alternativeDistributionPackageVariants/{id}') twice. There is no plain-language statement of what an 'alternative distribution package variant' is or what retrieving one accomplishes, so it is effectively a tautology that an agent cannot distinguish meaningfully from sibling get_instance tools.

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

Usage Guidelines1/5

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

No guidance whatsoever on when to use this tool versus the many sibling retrieval tools (e.g. alternative_distribution_package_versions_variants_get_to_many_relationship, alternative_distribution_package_deltas_get_instance). No prerequisites, exclusions, or alternatives 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