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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_prices_create_instance

Creates a subscription price in App Store Connect via the subscriptionPrices endpoint, letting you define pricing for an auto-renewable subscription.

Instructions

POST /v1/subscriptionPrices (POST /v1/subscriptionPrices) Body shape: see OpenAPI components.schemas.SubscriptionPriceCreateRequest 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_prices_create_instance"
  }
}

Input Schema

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

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?

With no annotations, the description carries the full burden of behavioral disclosure, but it only names the endpoint and points at the request schema. It says nothing about authentication requirements, side effects, idempotency, or the consequences of creating a price, which matters for a mutating POST.

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?

The text is short and front-loads the endpoint, but it wastes space duplicating the path in parentheses ("POST /v1/subscriptionPrices (POST /v1/subscriptionPrices)") and the schema pointer does not compensate for the missing purpose statement.

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 loosely-typed nested body (additionalProperties: {}), the description is too thin: it does not explain required body fields, relationships, or outcomes, leaving the agent under-informed about how to construct a valid create call.

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% for the single 'body' parameter, and the description usefully redirects to components.schemas.SubscriptionPriceCreateRequest. Baseline 3 applies since the schema does the heavy lifting and the description adds only a pointer.

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 only restates the HTTP verb and path ("POST /v1/subscriptionPrices"), which essentially repeats what the tool name 'subscription_prices_create_instance' already conveys. It never explains what a subscription price is or what the operation actually accomplishes, so an agent gets no purpose beyond the name.

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 indication of when to use this tool versus related siblings such as subscription_prices_delete_instance or the subscriptions_prices_get_to_many_relationship family, nor any note on prerequisites (e.g., which subscription or price point the body must reference). No usage guidance is present.

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