Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_bundle_ids

Find and list bundle IDs registered to your Apple Developer team, with filters for platform, name, seed ID, or identifier.

Instructions

Find and list bundle IDs that are registered to your team

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": "list_bundle_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for the results
limitNoMaximum number of bundle IDs to return (default: 100, max: 200)
filterNo
includeNoRelated resources to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only mentions scope ('registered to your team') but does not disclose read-only nature, rate limits, or whether it returns only owned IDs. For a listing operation with no annotations, more behavioral context is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that states the tool's purpose without any redundant information. It is front-loaded and efficient.

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?

Given the tool's complexity (4 parameters, nested objects, no output schema), the description is too brief. It does not explain how to use filter, sort, or include parameters, nor does it describe the response format. More detail is needed for a complete understanding.

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 coverage is high (all parameters have descriptions). The description adds no additional meaning beyond what the schema already provides. Baseline score is appropriate as the schema does the heavy lifting.

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

Purpose5/5

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

The description clearly states the tool's purpose: to find and list bundle IDs registered to the user's team. It uses a specific verb ('list') and resource ('bundle IDs'), which distinguishes it from siblings like 'get_bundle_id_info' (single item) and 'create_bundle_id' (creation).

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

Usage Guidelines3/5

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

The description implies usage for listing bundle IDs but provides no explicit guidance on when to use this tool versus alternatives like 'get_bundle_id_info' for a single ID or 'create_bundle_id' for creation. It lacks explicit when-not or alternative suggestions.

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