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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

marketplace_search_details_delete_instance

Deletes a specific marketplace search detail from App Store Connect by its ID. Use it to remove outdated or incorrect search metadata for a marketplace listing.

Instructions

DELETE /v1/marketplaceSearchDetails/{id} (DELETE /v1/marketplaceSearchDetails/{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": "marketplace_search_details_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?

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare route. It does not state that the operation is destructive, whether deletion is reversible, what permissions are required, or how related resources are affected.

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?

It is short, but it is not concise in a useful sense: the same route string is printed twice in parentheses, which is redundant filler. There is no front-loaded explanation of purpose or effect.

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 operation with no annotations, no output schema, and no parameter guidance in the description, the definition is completely inadequate. An agent has no information about consequences, permissions, or expected 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% for the single 'id' parameter, so the schema already documents it fully and the baseline of 3 applies. The description adds nothing beyond echoing the path placeholder, offering no syntax, format, or identifier-source guidance.

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 merely restates the tool name as a raw HTTP route, 'DELETE /v1/marketplaceSearchDetails/{id}', duplicated in parentheses. While the HTTP verb hints at a deletion of a marketplace search detail resource, it offers no differentiation from the many sibling delete_instance tools and no explanation of what the resource is.

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 guidance whatsoever about when to use this tool, what prerequisites exist, or what alternatives (e.g., update_instance, create_instance) exist among the siblings. The agent is left to infer everything from the name.

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