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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_asset_library_ref_data_get_collection

Retrieve App Store app asset library reference data, including features, placement types, image and video specs, and display classes. Filter by specs, features, or placement groups.

Instructions

GET /v1/appAssetLibraryRefData (GET /v1/appAssetLibraryRefData)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
filter_specsNofilter by specs
filter_featuresNofilter by attribute 'features'
filter_placementTypesNofilter by attribute 'placementTypes'
fields_appAssetLibraryRefDataNothe fields to include for returned resources of type appAssetLibraryRefData
filter_placementProfileGroupsNofilter by attribute 'placementProfileGroups'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.4/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 entire behavioral burden, yet it discloses nothing: no auth requirements, no pagination behavior, no rate limits, and no note that this is a read-only collection fetch. Restating the URL conveys zero 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 parenthetical is a verbatim duplicate of the path, so the text is pure redundancy rather than efficient communication. Brevity here reflects under-specification, not conciseness.

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 five query parameters, a collection GET tool requires at least some description of purpose or filtering behavior. The description supplies none, leaving the agent unable to call it correctly beyond guessing from the endpoint name.

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%, so the five filter/fields parameters are already documented in the schema (filter_specs, filter_features, filter_placementTypes, filter_placementProfileGroups, fields_appAssetLibraryRefData). Per the high-coverage baseline this is a 3, though the description itself contributes nothing about filter syntax or combinations.

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

Purpose1/5

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

The description is a literal restatement of the HTTP path, duplicated parenthetically: 'GET /v1/appAssetLibraryRefData (GET /v1/appAssetLibraryRefData)'. It adds no verb, resource meaning, or scope beyond what the tool name already encodes, and gives no differentiation from siblings like app_asset_library_ref_data_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 about when to call this versus alternatives, no prerequisites, and no mention of the sibling single-instance endpoint. An agent has no basis for choosing this tool over the collection/relationship siblings.

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