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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

background_asset_versions_get_instance

Retrieve a specific background asset version by ID from App Store Connect to inspect its state, version, platform, locale, and related release or file data.

Instructions

GET /v1/backgroundAssetVersions/{id} (GET /v1/backgroundAssetVersions/{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": "background_asset_versions_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_backgroundAssetsNothe fields to include for returned resources of type backgroundAssets
fields_backgroundAssetVersionsNothe fields to include for returned resources of type backgroundAssetVersions
fields_backgroundAssetUploadFilesNothe fields to include for returned resources of type backgroundAssetUploadFiles
fields_backgroundAssetVersionAppStoreReleasesNothe fields to include for returned resources of type backgroundAssetVersionAppStoreReleases
fields_backgroundAssetVersionExternalBetaReleasesNothe fields to include for returned resources of type backgroundAssetVersionExternalBetaReleases
fields_backgroundAssetVersionInternalBetaReleasesNothe fields to include for returned resources of type backgroundAssetVersionInternalBetaReleases

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 carries the full behavioral burden, and it discloses nothing: not authentication requirements, not pagination or rate limits, not what the include/fields_* parameters actually expand, and not whether the id must exist. The endpoint path alone is not behavioral context.

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 only content is the same endpoint string repeated twice in parentheses, which is pure redundancy rather than front-loaded purpose. It is under-specified, not concise.

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?

For an 8-parameter GET with no annotations and no output schema, the description supplies nothing an agent needs: no resource semantics, no note on sparse fieldsets or relationship expansion, and no return-value context.

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%, with every one of the 8 parameters documented in the schema (including the include and fields_* sparse-fieldset options), so the baseline of 3 applies. The description adds no additional meaning about id format or how relationship inclusion interacts with the returned payload.

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 is just the raw HTTP path 'GET /v1/backgroundAssetVersions/{id}', duplicated verbatim in parentheses. It restates what the tool name already encodes (get a background asset version by id) without adding any distinguishing detail versus siblings like background_assets_get_instance or background_asset_version_app_store_releases_get_instance.

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?

There is no guidance whatsoever on when to use this tool, when to prefer a sibling such as background_assets_versions_get_to_many_relationship, or what prerequisites (auth, existing id) apply.

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