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

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_bundle_id

Update a bundle ID's name while keeping its identifier unchanged.

Instructions

Update a bundle ID's name. Note: The identifier cannot be changed.

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": {
      "bundleIdId": "<bundleIdId>",
      "name": "<name>"
    },
    "name": "update_bundle_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdIdYesThe bundle ID resource ID
nameYesThe new name for the bundle ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Lacking annotations, the description carries full responsibility. It discloses that the identifier cannot be changed, but omits side effects, required permissions, input validation behavior, or error conditions for a mutation operation.

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?

Two sentences, no redundant information. Every part earns its place, with the note front-loaded after the main action statement.

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 no output schema, the description should clarify return values or confirmation. It does not. The tool is simple, but lacks context on success/error responses, rate limits, or permission requirements.

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 100% and accurately describes both parameters. The description adds the note about immutable identifier, which is indirectly relevant to parameters, but does not enrich parameter meaning beyond the schema's 'bundleIdId' and 'name' descriptions.

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 updates a bundle ID's name, with a specific verb ('Update') and resource ('bundle ID'), and includes a critical note about the identifier being unchangeable, distinguishing it from create_bundle_id and delete_bundle_id among siblings.

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 explicit guidance on when to use this tool versus alternatives. While the note about immutable identifier implies when not to use it, there is no mention of prerequisites, typical use cases, or comparisons with other tools like create_bundle_id.

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