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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_info_localizations_delete_instance

Deletes a specific App Store app info localization by ID, removing locale-specific metadata from an app info resource.

Instructions

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

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it discloses nothing. A DELETE operation is destructive and irreversible, yet there is no mention of permission requirements, cascading effects, confirmation semantics, or whether the deletion can be undone.

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 wastes its only content by duplicating the same path string twice in parentheses, and it is not front-loaded with anything an agent can act on. This is under-specification rather than genuine conciseness.

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

Completeness1/5

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

For a destructive delete tool with no annotations, no output schema, and no explanatory text, the definition is completely inadequate. An agent cannot determine what gets deleted, what happens on success, or what errors to expect from this description alone.

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% and the single 'id' parameter is documented in the schema as 'the id of the requested resource', so the schema already does the work. The description adds no format, type, or sourcing detail for the id, which is the baseline-3 outcome when schema coverage is high.

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 restated as an HTTP verb and path: 'DELETE /v1/appInfoLocalizations/{id}'. It conveys a delete operation on a localizations resource, but adds no plain-language purpose and does not distinguish this endpoint from sibling tools such as app_info_localizations_update_instance or app_info_localizations_get_instance beyond the verb embedded in the name.

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?

No guidance whatsoever about when to use this tool, what prerequisites exist, or what alternatives handle related operations. The agent gets no context for choosing a delete over an update or for knowing what state the resource must be in.

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