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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

users_visible_apps_create_to_many_relationship

Assign visible apps to a user by creating to-many relationships in App Store Connect, controlling which apps the user can access.

Instructions

POST /v1/users/{id}/relationships/visibleApps (POST /v1/users/{id}/relationships/visibleApps) Body shape: see OpenAPI components.schemas.UserVisibleAppsLinkagesRequest for the full JSON:API envelope.

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>",
      "body": "<body>"
    },
    "name": "users_visible_apps_create_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.UserVisibleAppsLinkagesRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden yet discloses nothing beyond the endpoint. It does not say that this is an additive relationship mutation, whether it requires specific scopes/auth, what happens on duplicates, or how it differs from a replace. This is a significant gap for a write operation.

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 short and front-loaded with the endpoint, but the parentheses literally repeat the same path verbatim, which is pure waste. There is little else, so conciseness is achieved at the cost of substance.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits the relationship semantics (append vs replace), any auth/permission context, and the effect on the user's visible apps list, leaving the agent under-informed for correct invocation.

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%, so both the id and body parameters are already documented structurally. The description points to the components.schemas.UserVisibleAppsLinkagesRequest envelope, but the schema body description already says this, so no new meaning is added. Baseline 3 applies.

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

Purpose3/5

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

The description only restates the HTTP method and path, essentially duplicating itself in parentheses. The resource (users' visibleApps relationships) and the create/add semantics are inferable from the name and path, but the prose never states in plain language what the tool does or distinguishes it from replace/delete/get siblings.

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 about when to use this additive relationship call versus the sibling users_visible_apps_replace_to_many_relationship, users_visible_apps_delete_to_many_relationship, or users_visible_apps_get_to_many_relationship. The agent is left to infer that this appends visible apps rather than replacing them.

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