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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_prices_delete_to_many_relationship

Remove price associations from a subscription by deleting the to-many relationship between the subscription and its prices.

Instructions

DELETE /v1/subscriptions/{id}/relationships/prices (DELETE /v1/subscriptions/{id}/relationships/prices) Body shape: see OpenAPI components.schemas.SubscriptionPricesLinkagesRequest for the full JSON:API envelope.

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>",
      "body": "<body>"
    },
    "name": "subscriptions_prices_delete_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.SubscriptionPricesLinkagesRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It only implies mutation via the DELETE verb; it does not say what is destroyed (the relationship only, or the underlying price objects), whether it is reversible, what permissions are needed, or how the JSON:API linkage body affects the result. That is a significant gap for a destructive to-many delete.

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

Conciseness3/5

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

It is short, but the endpoint path is repeated twice with zero added value, and it leads with a URL rather than a purpose statement. Brevity is present but not well spent.

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 relationship-delete with a nested, opaque JSON:API body, no annotations, and no output schema, the description leaves the agent without the essentials: what actually happens to the prices, or an inline description of the linkage payload the agent must construct. Pointing at an external OpenAPI component the agent cannot see does not fill the gap.

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%, with both 'id' and 'body' documented in the schema, so the baseline is 3. The description's reference to components.schemas.SubscriptionPricesLinkagesRequest duplicates the schema's own body description and adds no new syntax or meaning.

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

Purpose3/5

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

The description conveys an HTTP verb (DELETE) on a specific resource path (subscriptions/{id}/relationships/prices), so the operation is inferable. However it is stated only as a raw endpoint URL, duplicated verbatim, with no plain-language statement of what is being removed (price linkages vs. price records) and no differentiation from the sibling subscriptions_prices_get_to_many_relationship.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the sibling GET/replace operations. The agent is given only the endpoint and must guess the context entirely.

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