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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

review_submission_items_delete_instance

Delete a review submission item by its ID to remove it from an App Store review submission.

Instructions

DELETE /v1/reviewSubmissionItems/{id} (DELETE /v1/reviewSubmissionItems/{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": "review_submission_items_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/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, yet it only discloses the HTTP verb DELETE. It says nothing about irreversibility, required scopes/permissions, cascading effects on the parent review submission, or the response (e.g., 204 No Content). The verb alone hints at a destructive operation, but that is the sole signal.

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 not concise: the identical route string is printed twice, which is pure duplication with zero informational value. It is under-specified rather than efficiently front-loaded.

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 single-parameter delete with no annotations and no output schema, the description should at least confirm the operation's effect and outcome. Instead it leaves the agent to infer everything from the verb and path, which is inadequate even for a simple mutation.

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?

There is exactly one parameter and schema description coverage is 100%, so the schema already documents 'id' as 'the id of the requested resource'. The description adds nothing beyond restating it as a path placeholder, which is the expected baseline when the schema does the work.

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 only echoes the tool name in HTTP form: 'DELETE /v1/reviewSubmissionItems/{id}', repeated verbatim in parentheses. It does convey a delete operation on review submission items, but it is tautological rather than an explanatory statement, and it does not distinguish this tool from siblings like review_submission_items_update_instance or review_submission_items_create_instance.

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 on when to use this tool, when not to, or what alternatives exist. An agent gets no indication of prerequisites (e.g., the parent review submission must exist) or the sibling tool to use for other operations.

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