Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_introductory_offers_create_instance

Create a subscription introductory offer to configure free trials or promotional pricing for new subscribers in App Store Connect.

Instructions

POST /v1/subscriptionIntroductoryOffers (POST /v1/subscriptionIntroductoryOffers) Body shape: see OpenAPI components.schemas.SubscriptionIntroductoryOfferCreateRequest for the full JSON:API envelope.

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": {
      "body": "<body>"
    },
    "name": "subscription_introductory_offers_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.SubscriptionIntroductoryOfferCreateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It is a mutation (POST/create) but says nothing about authentication needs, side effects, whether the operation is idempotent, or what happens on failure. The only added context is a pointer to the OpenAPI request schema, which is a partial aid.

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

Conciseness3/5

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

It is short, but the endpoint path is duplicated verbatim ('POST /v1/subscriptionIntroductoryOffers' twice), which is wasteful. The remaining content is a single terse pointer to the OpenAPI schema.

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

Completeness2/5

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

For a create operation with a required nested JSON:API body, no output schema, and no annotations, the description is thin. It does not explain the resource, required payload semantics, or return expectations, leaving the agent to resolve everything through the external OpenAPI document.

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 'body' parameter whose schema already documents the shape reference. The description merely repeats that pointer (components.schemas.SubscriptionIntroductoryOfferCreateRequest), adding little beyond the schema baseline.

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

Purpose3/5

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

The description states the HTTP verb and endpoint (POST /v1/subscriptionIntroductoryOffers), which implies creating a subscription introductory offer resource. However, it never uses a natural-language verb like 'create', and it offers no differentiation from siblings such as subscription_introductory_offers_update_instance or subscription_introductory_offers_delete_instance. It is essentially a restatement of the name plus path.

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

Usage Guidelines2/5

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

There is no guidance about when to call this tool versus update/delete siblings, nor any prerequisite or context about what an introductory offer is. The agent must infer usage entirely from the name and endpoint.

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