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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_groups_versions_get_to_many_related

List versions for a subscription group by ID; filter by state and include localizations or group details.

Instructions

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

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": "subscription_groups_versions_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_stateNofilter by attribute 'state'
limit_localizationsNomaximum number of related localizations returned (when they are included)
fields_subscriptionGroupsNothe fields to include for returned resources of type subscriptionGroups
fields_subscriptionGroupVersionsNothe fields to include for returned resources of type subscriptionGroupVersions
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 burden, and it discloses nothing: not pagination behavior, not that include/limit_localizations are needed to retrieve nested resources, not any auth requirement. A read endpoint's behavioral profile is entirely absent.

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 only because it is under-specified, and the same path is stated twice with no added information in the second copy. Brevity achieved through redundancy is not effective conciseness.

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 high-complexity list endpoint with 8 parameters covering filtering, pagination, relationship inclusion, and sparse fieldsets, plus no annotations and no output schema. The description explains none of this and leaves the agent to reverse-engineer everything from the schema.

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, filter_state, limit_localizations, and three fields_* sparse fieldsets) are documented in the schema itself. The description adds zero semantic value, but the baseline is 3 when the schema does the heavy lifting.

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 restatement of the HTTP path, duplicated verbatim in parentheses, so it functions as a tautology rather than an explanation. An agent can infer 'fetch subscription group versions' from the URL slug, but the definition makes no attempt to say what a subscription group version is or how this differs from the sibling subscription_groups_versions_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 when-to-use guidance, no prerequisites, and no mention of the near-identical sibling tool. The agent is given no basis for choosing this over subscription_groups_versions_get_to_many_relationship or subscription_groups_get_instance.

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