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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_app_availability_v2_get_to_one_related

Get an app's availability configuration and territory availabilities by app ID to determine where it is available on the App Store.

Instructions

GET /v1/apps/{id}/appAvailabilityV2 (GET /v1/apps/{id}/appAvailabilityV2)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appAvailabilitiesNothe fields to include for returned resources of type appAvailabilities
limit_territoryAvailabilitiesNomaximum number of related territoryAvailabilities returned (when they are included)
fields_territoryAvailabilitiesNothe fields to include for returned resources of type territoryAvailabilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/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 of behavioral disclosure, and it discloses nothing. It does not state permissions, side effects, auth requirements, or return characteristics beyond the bare path.

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 fails the 'every sentence earns its place' test: the parenthetical simply repeats the identical path verbatim, adding zero information. Under-specification rather than true conciseness.

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 GET-instance tool with a rich, fully documented schema but no output schema and no annotations, the description should at minimum explain what resource is fetched and how to differentiate it from the near-identical sibling relationship tool. It leaves the agent without the context needed to select it correctly.

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 the schema already documents all five parameters (id, include, field selectors, and limit). The description adds no parameter meaning, which is acceptable given the schema does the heavy lifting, but it contributes nothing.

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 verb and endpoint path repeated twice in parentheses, not a plain-language statement of purpose. It conveys 'GET appAvailabilityV2 for an app' only implicitly through the URL, and gives no functional characterization that would distinguish it from sibling tools like apps_app_availability_v2_get_to_one_relationship or app_availabilities_v2_get_instance.

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 on when to use this tool versus the many sibling availability tools, no prerequisites, and no exclusions. The agent is left to infer everything from the endpoint string.

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