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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_price_points_get_to_many_related

Retrieve all price points for a specific subscription ID to manage pricing across territories and plan types.

Instructions

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

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_price_points_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_planTypeNofilter by planType
filter_territoryNofilter by id(s) of related 'territory'
fields_territoriesNothe fields to include for returned resources of type territories
filter_upfrontPricePointIdNofilter by upfrontPricePointId
fields_subscriptionPricePointsNothe fields to include for returned resources of type subscriptionPricePoints

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 read-only/idempotency statement, no pagination or rate-limit behavior, no auth requirements. The bare 'GET' verb is the only hint, and it is implicit rather than explained.

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 text is short but not concise in any useful sense: it duplicates the identical path in parentheses, so half the content is pure redundancy and nothing is front-loaded as a purpose statement.

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 an 8-parameter list endpoint with no annotations and no output schema, the description supplies none of the context an agent needs (what a price point is, how results are paged, what the filters do). It is completely inadequate given 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% for all 8 parameters (id, limit, include, filters, fields_*), so the schema already documents every parameter. The description adds no syntax, format, or meaning beyond that, which is the baseline 3 case 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 only the HTTP method and path, 'GET /v1/subscriptions/{id}/pricePoints', repeated twice. It restates the tool name (subscriptions_price_points_get_to_many_related) in URL form rather than stating in plain language what the tool does or how it differs from siblings like subscriptions_price_points_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, when-not-to-use, or alternative guidance at all. An agent cannot tell from this text when to prefer this endpoint over subscriptions_price_points_get_to_many_relationship or subscription_price_points_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