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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

background_asset_upload_files_get_instance

Retrieves details for a specific background asset upload file by ID, letting you inspect its upload state, file metadata, checksums, and upload operations.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_backgroundAssetUploadFilesNothe fields to include for returned resources of type backgroundAssetUploadFiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/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: no auth/permission requirements, no note that this is a non-mutating read, no pagination or sparse-fieldset behavior. The duplicated endpoint string adds zero behavioral context beyond the name.

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 path printed twice in parentheses, which is pure redundancy rather than concision. Nothing is front-loaded in natural language and no information earns its place.

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

Completeness2/5

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

For a single-resource GET with full schema coverage and no output schema, the definition is technically enough to construct a call, but it omits what the resource represents, the id source, and any behavioral caveats. Given the very large sibling surface of similarly named tools, that omission leaves the agent under-equipped.

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% (both 'id' and 'fields_backgroundAssetUploadFiles' are documented in the schema), so the baseline of 3 applies even though the description says nothing about parameters. The description adds no extra meaning such as id format or how the sparse fieldset interacts with the response.

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 only the raw endpoint string repeated twice, so the 'purpose' is inferred purely from the HTTP verb and path rather than stated. It does convey 'fetch one background asset upload file by id', which is marginally more than a bare tautology, but there is no plain-language statement of what the resource is or how it differs from background_asset_upload_files_create_instance / update_instance / the related-list tool.

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 when-to-use guidance, no preconditions, no alternatives named. The sibling set contains create, update, and a to-many relationship variant of the same resource, and nothing in the description tells the agent which to pick or when this single-instance read is appropriate.

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