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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_plan_availabilities_get_to_many_relationship

Retrieve the plan availability relationships for a specific subscription ID to inspect linked availability plans, with an optional pagination limit.

Instructions

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

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_plan_availabilities_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

C2/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. There is no mention of authentication requirements, pagination behavior (despite a limit parameter), ordering, or what the returned relationship objects contain.

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 line is not concise in a useful sense: the parenthetical duplicates the identical string already given, so every token is redundant rather than informative. Brevity here reflects under-specification, not efficiency.

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?

With no annotations and no output schema, the description is the only source of behavioral context, and it supplies none. For a relationship-listing endpoint, an agent gets no idea what the returned plan availabilities represent or how they relate to the parent subscription.

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%, so both 'id' and 'limit' are already documented in the schema and the description need not duplicate them. The description adds no parameter meaning 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 the URL path repeated verbatim in parentheses, which restates the tool name rather than explaining it. It does not say what a 'plan availability' relationship is or what listing them yields, so an agent cannot distinguish it from siblings like subscriptions_plan_availabilities_get_to_many_related or subscription_plan_availabilities_available_territories_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 Guidelines2/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 mention of prerequisites, and no guidance on choosing between this and the many adjacent relationship tools. The HTTP path implies a read of a related collection, but nothing in the text tells the agent when this tool is the right one.

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