Skip to main content
Glama

App Store Rejection Help

Explain a store rejection

explain_rejection
Read-onlyIdempotent

Paste an App Store or Google Play rejection message and get, for each guideline, ITMS code or Play policy it cites: what it means, what to change, and the related automated checks. Nothing is stored.

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": {
      "message": "<message>"
    },
    "name": "explain_rejection"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe whole rejection message from App Store Connect (Resolution Center) or Play Console, including the line that names the guideline or policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered. The description adds one genuinely useful piece of behavior beyond them: 'Nothing is stored,' a data-handling guarantee that readOnlyHint alone does not imply. It says nothing about how unrecognized or ambiguous codes in a pasted message are handled.

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 sentences, front-loaded with the input and output contract, with the privacy note trailing as a short clause. No filler and nothing repeated.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the three things returned per citation. Combined with the data-retention note, an agent knows enough to call it correctly. Minor gap: no mention of behavior for messages that cite nothing recognizable.

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% and there is a single required parameter whose schema already explains that the whole message including the naming line is wanted. The description's 'paste a rejection message' framing restates rather than extends that. Baseline 3 applies.

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 input (an App Store or Google Play rejection message) and a concrete output (per cited guideline/ITMS code/Play policy: meaning, what to change, related automated checks). That is far more than a restated name. It does not explicitly name or contrast with explain_guideline or list_common_rejections, so sibling differentiation is left implicit.

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

Usage Guidelines4/5

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

The use context is clear: you have a full rejection message pasted from App Store Connect Resolution Center or Play Console. It does not state when to prefer explain_guideline (single guideline lookup) or list_common_rejections instead, nor does it set any exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources