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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_promotional_offers_get_to_many_relationship

Retrieve the promotional offer IDs linked to a specific subscription, with optional pagination, to map and manage offers tied to that subscription.

Instructions

GET /v1/subscriptions/{id}/relationships/promotionalOffers (GET /v1/subscriptions/{id}/relationships/promotionalOffers)

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_promotional_offers_get_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/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 behavioral burden, and it delivers almost nothing: no auth requirements, no pagination behavior despite a limit parameter existing, no statement of what the payload contains (linkage identifiers vs. full resources). The only signal is the implicit read-only nature of an HTTP GET, which is thin credit.

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?

It is short, but the same URL string is printed twice with zero added information, which is pure redundancy rather than conciseness. There is no front-loaded explanation of intent.

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

Completeness1/5

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

For a relationship endpoint with no annotations and no output schema, the agent has no idea whether the response is a list of resource IDs or full objects, how pagination works, or how it differs from the sibling 'related' tool. Nothing an agent needs in order to call it correctly is present.

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 both parameters (id, limit) are documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or default information beyond what the schema already states.

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 a bare URL restatement of the tool name, duplicated verbatim in parentheses. It does encode a verb (GET) and a resource path (subscriptions/{id}/relationships/promotionalOffers), so an agent can dimly infer it lists promotional-offer relationships for a subscription, but there is no prose explaining the operation and nothing distinguishes it from the sibling subscriptions_promotional_offers_get_to_many_related.

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?

No when-to-use guidance, no prerequisites, no mention of the near-identical 'related' sibling that also returns promotional offers. The agent is left to guess which of the two endpoints it should call.

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