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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscriptions_offer_codes_get_to_many_relationship

Retrieve the offer codes linked to a specific subscription in App Store Connect, with optional pagination to fetch many related resources.

Instructions

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

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

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 pagination behavior, no auth/permission requirements, no return shape. The bare 'GET' verb weakly implies a read, but that is already in the tool name, not added value.

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 not concise in a useful sense: the identical endpoint string is repeated in parentheses, which is redundant padding rather than information. Nothing is front-loaded because there is no substance to front-load.

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 a relationship-listing tool with no annotations, no output schema, and no prose, the description is completely inadequate. An agent cannot tell what an 'offerCode' relationship contains, how results are paginated, or when this differs from the many related sibling endpoints.

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% with both 'id' and 'limit' documented in the schema, so the baseline of 3 applies. The description adds no syntax or format detail beyond what the schema already provides.

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 only restates the HTTP route 'GET /v1/subscriptions/{id}/relationships/offerCodes' twice, which is effectively a tautology of the tool name. It does not state in prose what the tool returns or distinguishes it from siblings like subscriptions_offer_codes_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?

No when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., the '..._get_to_many_related' variant or subscription_offer_codes_get_instance). The agent must infer everything from the endpoint path.

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