Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_app_screenshot

Delete a screenshot from a screenshot set using its appScreenshotId to remove outdated or incorrect images from App Store listings.

Instructions

Delete a screenshot from a screenshot set

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": {
      "appScreenshotId": "<appScreenshotId>"
    },
    "name": "delete_app_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
appScreenshotIdYesThe ID of the screenshot to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

C2.9/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 does little beyond the verb. It never states that deletion is irreversible, whether it requires specific App Store Connect permissions, whether the containing screenshot set is affected, or what the call returns.

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

Conciseness4/5

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

A single tight sentence with no filler, front-loaded with the verb. It is appropriately sized for a one-parameter tool, though it is too sparse to demonstrate real structural craft.

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 operation with no annotations and no output schema, the description is thin. An agent gets no warning about consequences, permission requirements, or failure modes, which is a meaningful gap for a delete tool.

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 a single required appScreenshotId, so the schema already fully documents the parameter. The description adds no format, sourcing, or lookup guidance beyond what the schema provides, which is the baseline 3 case.

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

Purpose4/5

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

States a specific verb (Delete) and resource (a screenshot) plus its container scope (from a screenshot set), so the operation is unambiguous. It does not differentiate itself from the numerous sibling screenshot tools (upload_app_screenshot, list_app_screenshots, create_app_screenshot_set), but the destructive verb alone makes its role clear.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as uploading or listing screenshots. The agent must infer that this is the terminal cleanup step of a screenshot workflow.

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