Skip to main content
Glama
Sign In
app-publish-mcp

app-publish-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apple_delete_screenshot

Deletes a screenshot by ID through the deprecated screenshot-set API. Use placement and asset deletion tools for Asset Library media instead.

Instructions

Legacy: delete a screenshot from the deprecated screenshot-set API. Use apple_delete_placement and apple_delete_asset for Asset Library media.

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": {
      "screenshotId": "<screenshotId>"
    },
    "name": "apple_delete_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
screenshotIdYesScreenshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that this targets a deprecated API and names replacements, but never states that the deletion is permanent, what permissions are needed, or whether anything else is affected.

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?

Two short sentences, the legacy status and primary behavior front-loaded, with the redirect to alternatives second. No filler, though the 'Legacy:' label plus 'deprecated' is slightly redundant.

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

Completeness4/5

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

For a single-parameter legacy delete with no output schema, the agent knows which API it targets and where to go for modern media deletion. Only the destructive/irreversible nature and confirmation behavior are left unstated.

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?

Only one parameter ('screenshotId') with 100% schema coverage, so the schema already documents everything. The description adds no format, source, or ID-acquisition guidance beyond the deprecated-context framing.

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

Purpose5/5

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

States a specific verb and resource ('delete a screenshot') and immediately scopes it to the deprecated screenshot-set API, which distinguishes it from the Asset Library siblings it names.

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

Usage Guidelines5/5

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

Explicitly frames the tool as legacy and routes the agent to apple_delete_placement and apple_delete_asset for Asset Library media. The condition that selects the alternative is spelled out, not inferred.

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