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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

profiles_delete_instance

Delete a provisioning profile by ID from App Store Connect to remove unused or obsolete profiles from the account.

Instructions

DELETE /v1/profiles/{id} (DELETE /v1/profiles/{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": "profiles_delete_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/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 the full behavioral burden, and it discloses nothing beyond the fact of deletion. It does not state that the operation is irreversible, what related resources (certificates, devices, bundle id) are affected, or what permissions are required.

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?

The text is short but contains a verbatim duplicated parenthetical, which is pure noise rather than useful brevity. It is under-specified rather than concise: nothing beyond the endpoint string is present to earn its place.

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 destructive, irreversible-by-nature operation with no annotations and no output schema, the definition should at minimum describe consequences or required permissions. The raw route leaves the agent without the context needed to invoke it safely.

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% for the single 'id' parameter, so the schema already documents the input fully. The description adds no format, source, or lookup guidance beyond the raw path template, which is the baseline-3 case.

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 tool name expanded into an HTTP route: 'DELETE /v1/profiles/{id}' restates 'profiles_delete_instance' with no added meaning. It conveys the verb and resource, but does not distinguish this from the many other *_delete_instance siblings or explain what a profile is in this context.

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 guidance about when to delete a profile versus other operations (e.g., profiles_get_instance, profiles_create_instance), no prerequisites, and no warning about side effects. Only the barest implied usage ('delete the profile with this id') can be inferred from the route.

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