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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

user_invitations_get_collection

Retrieves App Store Connect user invitations for team management, with filters by email or role, sorting, and optional related app visibility.

Instructions

GET /v1/userInvitations (GET /v1/userInvitations)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user_invitations_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNocomma-separated list of sort expressions; resources will be sorted as specified
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
filter_emailNofilter by attribute 'email'
filter_rolesNofilter by attribute 'roles'
limit_visibleAppsNomaximum number of related visibleApps returned (when they are included)
filter_visibleAppsNofilter by id(s) of related 'visibleApps'
fields_userInvitationsNothe fields to include for returned resources of type userInvitations

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 burden of behavioral disclosure, yet it says nothing beyond the raw HTTP route. It does not mention pagination, sorting defaults, authentication requirements, or what the collection contains — all of which matter for a 9-parameter list endpoint.

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 text is short but not concise in the useful sense — it is under-specified and redundantly restates the path twice. Every character duplicates information already present in the tool name, so nothing earns its place.

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 9-parameter collection tool with no annotations and no output schema, the description should explain scope, filtering, and return shape. It provides none of this, leaving the definition effectively undocumented.

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 all 9 parameters (sort, limit, include, filters, field selectors) documented directly in the schema, so the baseline is 3. The description adds no parameter meaning at all, but the schema already does the heavy lifting.

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 merely echoes the tool name and HTTP verb ('GET /v1/userInvitations') with the path repeated twice in parentheses. It implies listing user invitations, but provides no verb beyond the HTTP method and no differentiation from siblings such as user_invitations_get_instance or user_invitations_create_instance. This is essentially a tautology of the tool name.

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 collection endpoint versus user_invitations_get_instance or user_invitations_visible_apps_get_to_many_related, and no mention of prerequisites or filters. The agent is left to infer everything from the name alone.

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