Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

disable_bundle_capability

Remove a capability from a bundle ID in App Store Connect to manage app features and permissions.

Instructions

Disable a capability for a bundle ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capabilityIdYesThe ID of the capability to disable

Implementation Reference

  • The handler function that executes the disable_bundle_capability tool. It validates the capabilityId argument and calls the AppStoreConnectClient to DELETE /bundleIdCapabilities/{capabilityId}, then returns a success message.
    async disableBundleCapability(args: {
      capabilityId: string;
    }): Promise<{ success: boolean; message: string }> {
      const { capabilityId } = args;
      
      validateRequired(args, ['capabilityId']);
    
      await this.client.delete(`/bundleIdCapabilities/${capabilityId}`);
    
      return { 
        success: true, 
        message: "Capability disabled successfully" 
      };
    }
  • The input schema definition for the disable_bundle_capability tool, specifying that capabilityId is a required string.
    {
      name: "disable_bundle_capability",
      description: "Disable a capability for a bundle ID",
      inputSchema: {
        type: "object",
        properties: {
          capabilityId: {
            type: "string",
            description: "The ID of the capability to disable"
          }
        },
        required: ["capabilityId"]
      }
    },
  • src/index.ts:1376-1377 (registration)
    The tool registration in the MCP server request handler switch statement, which routes calls to disable_bundle_capability to the bundleHandlers.disableBundleCapability method.
    case "disable_bundle_capability":
      return { toolResult: await this.bundleHandlers.disableBundleCapability(args as any) };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a destructive operation, requires specific permissions, has side effects, or what the expected outcome is (e.g., confirmation message, error handling).

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, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core action, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'disable' entails (e.g., reversible, immediate effect), error conditions, or return values, leaving significant gaps for an AI agent to understand the tool's behavior.

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 parameter 'capabilityId' is documented in the schema. The description doesn't add any extra meaning about the parameter beyond what's in the schema, such as format examples or where to find capability IDs.

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

Purpose4/5

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

The description clearly states the action ('disable') and target ('a capability for a bundle ID'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'enable_bundle_capability' beyond the opposite action, missing specific distinctions about when each is appropriate.

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 is provided on when to use this tool versus alternatives like 'enable_bundle_capability' or other bundle-related tools. The description lacks context about prerequisites, conditions for disabling, or what happens after disabling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/concavegit/app-store-connect-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server