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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bundle_ids_get_instance

Retrieve a specific App Store Connect bundle ID by its ID, with optional related profiles, capabilities, or app data.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
limit_profilesNomaximum number of related profiles returned (when they are included)
fields_profilesNothe fields to include for returned resources of type profiles
fields_bundleIdsNothe fields to include for returned resources of type bundleIds
limit_bundleIdCapabilitiesNomaximum number of related bundleIdCapabilities returned (when they are included)
fields_bundleIdCapabilitiesNothe fields to include for returned resources of type bundleIdCapabilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/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 burden of behavioral disclosure, and it discloses nothing: no auth/permission requirements, no rate-limit notes, no indication of what the response contains or how sparse fieldsets/includes behave. Just echoing the HTTP path adds zero behavioral context for a read tool with eight parameters.

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?

Extremely short, but this is under-specification rather than conciseness: the only content is a duplicated path string, with no front-loaded plain-language statement of what the call returns. It doesn't waste many words, but it wastes the one slot it has.

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 eight-parameter JSON:API-style read with relationship includes, sparse field selection, and no output schema or annotations to fall back on, the description omits everything an agent needs to call it correctly. It is wholly inadequate for the tool's complexity.

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% — all eight parameters (id, include, fields_*, limit_*) carry their own descriptions in the schema — so the baseline of 3 applies. The description adds no parameter meaning whatsoever, but it does not need to compensate for gaps because the schema already documents everything.

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 essentially the raw HTTP operation repeated twice — 'GET /v1/bundleIds/{id}' — which restates the tool name (bundle_ids_get_instance) rather than stating the purpose in language an agent can use. It does convey verb and resource, but it offers no distinguishing detail against siblings like bundle_ids_get_collection or bundle_ids_create_instance.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to fetch a single bundle ID versus the collection, and no prerequisites or exclusions. The endpoint-path fragment gives no routing signal for an agent choosing among the many sibling tools.

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