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

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_analytics_report_request

Delete an existing analytics report request to stop report generation and remove access to generated reports.

Instructions

Delete an analytics report request. This stops report generation and removes access to existing reports.

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": {
      "requestId": "<requestId>"
    },
    "name": "delete_analytics_report_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesThe analytics report request ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It reveals the destructive behavior (stops generation, removes access), but doesn't specify irreversibility, required permissions, or side effects on related data. It covers the core impact adequately but not comprehensively.

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

Conciseness5/5

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

Two short sentences convey the purpose and effect with no unnecessary words. The description is front-loaded and efficient, earning its place entirely.

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?

Given the simplicity of the tool (one required parameter, no output schema, no nested objects), the description is fairly complete. It explains what happens when the tool is used. Minor improvements could mention that the request must exist or the deletion is permanent, but overall it's sufficient.

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?

The single parameter 'requestId' is described in the schema as 'The analytics report request ID to delete'. The tool description does not add any additional meaning beyond that. Since schema coverage is 100%, a score of 3 is appropriate.

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?

The description clearly states the action ('Delete an analytics report request') and the resource. It also explains the effect: 'stops report generation and removes access to existing reports.' This distinguishes it from sibling tools like create, get, list, and download.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, it doesn't mention prerequisites (e.g., the request must exist) or caution against accidental deletion. It's adequate for a simple delete but lacks contextual advice.

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