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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

background_asset_version_internal_beta_releases_get_instance

Retrieve a specific internal beta release for a background asset version by ID, including its state and related background asset version details.

Instructions

GET /v1/backgroundAssetVersionInternalBetaReleases/{id} (GET /v1/backgroundAssetVersionInternalBetaReleases/{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_version_internal_beta_releases_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_backgroundAssetVersionsNothe fields to include for returned resources of type backgroundAssetVersions
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. The only signal is the 'GET' verb implying a read, but there is no mention of auth requirements, error behavior, whether the resource is beta-only, or rate limits.

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 content is a redundant parenthetical repetition of the same path with zero informational payload. Brevity here reflects emptiness rather than efficient communication.

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 a retrieval tool with four parameters, no output schema, and no annotations, the description explains nothing about the returned resource, its relationship to background asset versions, or how the include/fields parameters shape the response. It is not sufficient for an agent to call it correctly.

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 each of the four parameters (id, include, and two fields_* filters) documented in the schema itself, so the baseline of 3 applies. The description adds no additional meaning about parameter usage or formatting beyond the schema.

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 endpoint path repeated twice, with no natural-language statement of what the tool does. It implies a GET-by-id retrieval of a 'backgroundAssetVersionInternalBetaRelease' resource, but it is essentially a restatement of the name/URL rather than an explanation.

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 on when to use this tool versus any of the many sibling GET-instance tools (e.g. background_asset_versions_get_instance, background_asset_version_external_beta_releases_get_instance, background_asset_version_app_store_releases_get_instance). No conditions, prerequisites, 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