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

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_bundle_ids

Retrieve all bundle IDs registered in App Store Connect, with optional filtering by platform (iOS, macOS, tvOS, visionOS).

Instructions

List all bundle IDs registered in App Store Connect. Can filter by platform.

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
limitNoMaximum number of bundle IDs to return (1-200)
platformNoFilter by platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden. It only mentions listing and filtering, omitting crucial details like pagination, authentication, rate limits, or behavior with no results.

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?

Single sentence with 12 words, directly stating the tool's core function and optional filtering. No wasted text.

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

Completeness3/5

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

For a simple list tool with a fully described schema, the basic purpose is covered. However, missing behavioral context (e.g., pagination, result count) limits completeness.

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?

Input schema descriptions cover 100% of parameters. The description adds minimal value by rephrasing the platform filter but does not elaborate on the limit parameter. Baseline 3 is appropriate.

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 verb 'List', the resource 'bundle IDs', and the scope 'registered in App Store Connect', distinguishing it from sibling list tools.

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?

No guidance on when to use this tool versus alternatives like list_apps or create_bundle_id. Context signals and sibling tools are available, but the description does not help the agent choose.

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