Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ASC Create Subscription

asc_create_subscription
Destructive

Create an App Store Connect subscription product in a group; handles live writes via human approval and returns approval_required when needed.

Instructions

Create a subscription product inside a subscription group (live write, needs human approval).

Use when: hand-building a single product. Prefer store_setup for the whole spec. Returns: {ok, data: {data: {id, ...}}} or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
nameYesInternal reference name of the subscription product.
periodNoSubscription period enum: ONE_WEEK, ONE_MONTH, TWO_MONTHS, THREE_MONTHS, SIX_MONTHS or ONE_YEAR.ONE_YEAR
group_idYesApp Store Connect subscription group id.
product_idYesProduct identifier of the subscription, e.g. com.example.app.yearly.
approval_idNoApproval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id.
family_shareableNoWhether the subscription can be shared with family members; default false.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.5
    • addedInput schema / properties / approval_id / description
      Added value: +"Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id."
    • addedInput schema / properties / family_shareable / description
      Added value: +"Whether the subscription can be shared with family members; default false."
    • addedInput schema / properties / group_id / description
      Added value: +"App Store Connect subscription group id."
    • addedInput schema / properties / name / description
      Added value: +"Internal reference name of the subscription product."
    • addedInput schema / properties / period / description
      Added value: +"Subscription period enum: ONE_WEEK, ONE_MONTH, TWO_MONTHS, THREE_MONTHS, SIX_MONTHS or ONE_YEAR."
    • addedInput schema / properties / product_id / description
      Added value: +"Product identifier of the subscription, e.g. com.example.app.yearly."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already disclose destructive=true, idempotent=false, openWorld=true, so the safety profile is covered. The description adds real value beyond them: 'live write, needs human approval' and the 'approval_required refusal' outcome, which explain the human-in-the-loop gate the agent must expect. It stops short of detailing reversibility or timing, hence a 4 rather than 5.

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?

Three short lines, each earning its place: purpose, routing rule, return contract, all front-loaded with no filler.

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?

An output schema exists, so the return-value line is a helpful bonus rather than a necessity, and it flags the non-obvious approval_required refusal path. Combined with the approval flow documented in the schema, an agent has everything needed to call this 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 every parameter (including the approval_id retry flow) is fully documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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 ('Create a subscription product inside a subscription group'), which cleanly distinguishes it from siblings like asc_create_subscription_group and asc_finalize_subscription. The parenthetical scope '(live write, needs human approval)' sharpens it further.

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 the use condition ('Use when: hand-building a single product') and the preferred alternative ('Prefer store_setup for the whole spec'), routing the agent without inference.

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