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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_app_price_schedule_get_to_one_relationship

Retrieve the app price schedule relationship for a specified app in App Store Connect, so you can inspect or automate app pricing schedules.

Instructions

GET /v1/apps/{id}/relationships/appPriceSchedule (GET /v1/apps/{id}/relationships/appPriceSchedule)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.1/5.0
Behavior2/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 only implies read-only via the literal 'GET' token. It says nothing about authentication, pagination, error behavior, or what the relationship linkage contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short and front-loaded, but the same path is printed twice (once bare, once in parentheses), which is pure redundancy rather than earning its place.

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?

For a tool with no annotations and no output schema, the description should explain what the appPriceSchedule relationship returns and how it differs from the related-resource variant. Instead it leaves the agent with only a URL and a required id.

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 the single 'id' parameter, so the schema already documents it fully and the baseline is 3. The description's '{id}' placeholder mirrors the schema without adding format or meaning beyond it.

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 HTTP path echoed twice, with no prose explaining what the resource is. It identifies a GET verb and a target path, but 'relationships/appPriceSchedule' is opaque and the sibling apps_app_price_schedule_get_to_one_related is not distinguished from this 'relationship' variant.

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 many sibling tools that fetch app price schedule data (e.g. apps_app_price_schedule_get_to_one_related, app_price_schedules_get_instance). An agent has nothing to route on.

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