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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_introductory_offers_get_to_many_related

Retrieve introductory offers for an App Store subscription by ID. Filter results by territory and include related subscription, territory, or price point data.

Instructions

GET /v1/subscriptions/{id}/introductoryOffers (GET /v1/subscriptions/{id}/introductoryOffers)

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": {
      "id": "<id>"
    },
    "name": "subscriptions_introductory_offers_get_to_many_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
filter_territoryNofilter by id(s) of related 'territory'
fields_territoriesNothe fields to include for returned resources of type territories
fields_subscriptionsNothe fields to include for returned resources of type subscriptions
fields_subscriptionPricePointsNothe fields to include for returned resources of type subscriptionPricePoints
fields_subscriptionIntroductoryOffersNothe fields to include for returned resources of type subscriptionIntroductoryOffers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2/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 burden, and it discloses nothing beyond the GET verb implied by the path. It says nothing about pagination behavior, required auth scopes, filtering semantics, or what the returned collection contains.

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

Conciseness2/5

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

The single sentence is a duplicated URL with no front-loaded purpose, no punctuation structure, and no information gain. It is short but purely redundant rather than concise.

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 an 8-parameter relationship-listing endpoint with no annotations and no output schema, the description provides essentially no context. An agent must rely entirely on the schema to understand filtering, sparse fieldsets, and inclusion of related resources.

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 all 8 parameters (id, limit, include, filters, sparse fieldsets) are documented in the schema itself. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 is literally the HTTP path duplicated in parentheses, which restates the tool name rather than stating a purpose in plain language. An agent can infer 'list introductory offers for a subscription' only by decoding the URL, and there is no differentiation from the sibling subscriptions_introductory_offers_get_to_many_relationship.

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

Usage Guidelines1/5

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

There is no guidance about when to use this tool, what preconditions apply (e.g., the subscription id must exist), or how it differs from the near-identically-named sibling tool. Nothing in the text addresses usage context.

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