Skip to main content
Glama
Sign In
app-publish-mcp

app-publish-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apple_create_subscription_group

Create a subscription group in App Store Connect by providing the app ID and a reference name to organize subscription offerings.

Instructions

Create a subscription group

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": {
      "appId": "<appId>",
      "referenceName": "<referenceName>"
    },
    "name": "apple_create_subscription_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp ID
referenceNameYesReference name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It states 'create' implying mutation, but does not mention idempotency, irreversible effects, required permissions, or what happens if the group already exists. Lacks transparency for a creation operation.

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 description is a single sentence, but it is too brief and does not earn its place. It sacrifices completeness for brevity, lacking valuable details that could be added without significant verbosity.

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?

Given the simplicity of the tool (2 parameters, no output schema), the description is minimal. It does not explain what a subscription group is, how referenceName is used, or any constraints. Incomplete for a new user unfamiliar with App Store Connect.

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 coverage is 100% with descriptions for both parameters ('App ID', 'Reference name'). The tool description adds no additional meaning beyond the schema. Baseline of 3 is appropriate since the schema already provides the meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a subscription group' uses a specific verb and resource, clearly indicating creation of a subscription group. It distinguishes from sibling tools like delete and list. However, it could be more explicit about what a subscription group is in the context of Apple App Store Connect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention prerequisites such as needing an existing app (appId) or that groups are used for auto-renewable subscriptions. No exclusions or context provided.

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