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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_subscription_groups_get_to_many_related

Retrieve all subscription groups for a specific app, with sorting, filtering, pagination, and related data like subscriptions and localizations.

Instructions

GET /v1/apps/{id}/subscriptionGroups (GET /v1/apps/{id}/subscriptionGroups)

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": "apps_subscription_groups_get_to_many_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
sortNocomma-separated list of sort expressions; resources will be sorted as specified
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
limit_versionsNomaximum number of related versions returned (when they are included)
limit_subscriptionsNomaximum number of related subscriptions returned (when they are included)
fields_subscriptionsNothe fields to include for returned resources of type subscriptions
filter_referenceNameNofilter by attribute 'referenceName'
fields_subscriptionGroupsNothe fields to include for returned resources of type subscriptionGroups
filter_subscriptions_stateNofilter by attribute 'subscriptions.state'
fields_subscriptionGroupVersionsNothe fields to include for returned resources of type subscriptionGroupVersions
limit_subscriptionGroupLocalizationsNomaximum number of related subscriptionGroupLocalizations returned (when they are included)
fields_subscriptionGroupLocalizationsNothe fields to include for returned resources of type subscriptionGroupLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/5.0
Behavior1/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, and it discloses nothing: no pagination behavior, no default page size, no note that 'include' and 'limit_*' interact, no auth or rate-limit context. A pure endpoint string leaves every behavioral trait undocumented.

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 brevity comes from under-specification rather than efficiency, and the duplicated parenthetical is pure waste. Nothing is front-loaded because there is no content to front-load.

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?

This is a 13-parameter sparse-fieldset/relationship-expansion endpoint with no annotations and no output schema. The description explains none of the filtering, sorting, inclusion, or pagination semantics an agent must understand to call it correctly, making it wholly inadequate for the tool's complexity.

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 13 parameters carry their own descriptions (sort expressions, include relationships, per-relationship limits, sparse fieldsets), so the baseline of 3 applies. The description adds nothing beyond the schema, but the schema itself is thorough.

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 just the raw endpoint string repeated twice in parentheses; it restates the tool name rather than explaining what the tool does. An agent can infer 'fetch subscription groups for an app' only by parsing the URL path, and the parenthetical duplication adds no information.

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 exclusions, and no mention of the near-identical sibling apps_subscription_groups_get_to_many_relationship. The agent gets nothing to disambiguate among the many apps_*_get_to_many_related tools.

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