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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_price_points_v3_get_instance

Fetch a specific App Store Connect app price point by ID to view pricing details and optionally include related app or territory data.

Instructions

GET /v3/appPricePoints/{id} (GET /v3/appPricePoints/{id})

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
fields_territoriesNothe fields to include for returned resources of type territories
fields_appPricePointsNothe fields to include for returned resources of type appPricePoints

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 mention of auth requirements, rate limits, whether include/fields affect payload size, or error behavior for a missing id. A bare URL path is not behavioral disclosure.

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 it wastes its one sentence by repeating the identical endpoint string twice in parentheses. The duplicate conveys no additional information and leaves the definition under-specified rather than concise.

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 five-parameter endpoint with relationship-inclusion and sparse-fieldset options, no output schema, and no annotations. The description explains none of the resource, the include mechanics, or the response shape, so it is 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 five parameters (id, include, fields_apps, fields_territories, fields_appPricePoints) are documented directly in the schema with enums and descriptions. The description adds nothing beyond the schema, which is the baseline 3 when the schema does all the work.

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 raw endpoint path 'GET /v3/appPricePoints/{id}', duplicated in parentheses. It implies a single-resource fetch of an app price point, but adds no explanation of what an app price point is or how the v3 price point differs from sibling resources like app_price_points_v3_equalizations_get_to_many_related or subscriptions_price_points_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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance whatsoever about when to use this tool versus alternatives such as the equalizations relationship tools or apps_app_price_points_get_to_many_relationship. The agent is left to infer everything from the tool name.

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