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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_plan_availabilities_create_instance

Create a subscription plan availability record in App Store Connect to define which territories offer a specific subscription plan.

Instructions

POST /v1/subscriptionPlanAvailabilities (POST /v1/subscriptionPlanAvailabilities) Body shape: see OpenAPI components.schemas.SubscriptionPlanAvailabilityCreateRequest 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_plan_availabilities_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/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 behavioral burden, yet it discloses almost nothing beyond the POST verb implying a mutation. It does not state permissions required, side effects, whether creation requires a parent subscription reference, or idempotency behavior.

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 string is duplicated verbatim ("POST /v1/subscriptionPlanAvailabilities (POST /v1/subscriptionPlanAvailabilities)"), which is wasted space, and the text leads with mechanics rather than purpose.

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 mutation tool with no annotations, no output schema, and a nested request body, the description is inadequate. Pointing the agent to an external OpenAPI component (which the agent may not be able to resolve) leaves the payload construction effectively undocumented.

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?

With a single body parameter at 100% schema description coverage, the baseline is 3. The description adds a marginal hint about the JSON:API envelope, but otherwise only repeats the schema pointer already present in the schema itself.

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

Purpose2/5

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

The description merely restates the HTTP method and endpoint ("POST /v1/subscriptionPlanAvailabilities"), which is a tautology of the tool name's create_instance/POST semantics. It never explains in business terms what a 'subscription plan availability' is or what creating one accomplishes, so it does not distinguish itself from sibling create_instance tools.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as subscription_plan_availabilities_update_instance or the GET/relationship siblings. The agent is left to infer context entirely from the name.

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