Skip to main content
Glama
Sign In
pofky

asc-mcp

by pofky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Start a free 7-day Pro trial

asc_start_trial
Destructive

Start a free 7-day Pro trial with an email to unlock all 41 App Store Connect write and control tools immediately in this session, including blocked Pro actions; no credit card.

Instructions

Start a free 7-day Pro trial, no credit card, unlocking all 41 tools including the full write/control plane. Call this when a Pro tool is refused and the user wants to proceed, and also when they ask for something only a Pro tool can do (editing metadata, screenshots, builds, TestFlight, IAP, submitting, releasing, preflight, briefings, keyword or review intelligence) before you hit the refusal. Either way, ask for their email address first and never invent one. The trial activates in THIS session immediately, so you can retry the tool that was blocked without any restart. Free.

Input Schema

NameRequiredDescriptionDefault
toolNoThe tool whose gate prompted this, e.g. submit_for_review.
emailYesThe user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address, a one-way hash of their Issuer ID, the trial key with its start and end dates, and which tool they started from. Tell them the address gets the key, one reminder shortly before the trial ends and one note after it, and that each has an unsubscribe link or they can reply stop. Tell them it also saves the key on this machine (~/.asc-mcp/license.json) and adds it to any existing asc-mcp entry in their MCP client configs, leaving a .bak copy of each file it edits. All of it is deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.14
    • changedInput schema / properties / email / description
      Previous value: -"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address and a one-way hash of their Issuer ID, nothing else, and both are deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy)."New value: +"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address, a one-way hash of their Issuer ID, the trial key with its start and end dates, and which tool they started from. Tell them the address gets the key, one reminder shortly before the trial ends and one note after it, and that each has an unsubscribe link or they can reply stop. Tell them it also saves the key on this machine (~/.asc-mcp/license.json) and adds it to any existing asc-mcp entry in their MCP client configs, leaving a .bak copy of each file it edits. All of it is deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy)."
  2. Changed1 schema field changedv1.9.11
    • changedInput schema / properties / email / description
      Previous value: -"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one."New value: +"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address and a one-way hash of their Issuer ID, nothing else, and both are deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy)."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavioral context beyond the readOnlyHint=false/destructiveHint=true annotations: the trial activates in the current session and the blocked tool can be retried without restart, and it insists the email be requested (never invented). However, the concrete destructive effects (rewriting MCP client configs, writing ~/.asc-mcp/license.json, .bak copies) are only disclosed in the schema's email field, not the description itself.

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?

Purpose is front-loaded in the opening clause and the two usage triggers follow logically. It is dense and runs long, with the email instruction duplicated from the schema, but nearly every sentence carries actionable guidance and nothing is buried.

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

Completeness5/5

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

For a 2-parameter trial-starter with no output schema, the description covers activation timing, session persistence, retry behavior, and the consent requirement. An agent has everything needed to invoke it correctly.

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%, so both the email and tool parameters are already fully documented there. The description only reinforces 'ask for their email first and never invent one,' which largely repeats the schema rather than adding new semantic meaning — a baseline 3.

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 (start) and resource (free 7-day Pro trial) and immediately quantifies the benefit: 'unlocking all 41 tools including the full write/control plane.' No sibling tool does this, so an agent can distinguish it without opening any schema.

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 names both trigger conditions ('when a Pro tool is refused and the user wants to proceed' and 'when they ask for something only a Pro tool can do... before you hit the refusal') and enumerates the Pro capabilities. This is exactly the when-to-use routing an agent needs.

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