Skip to main content
Glama
Sign In
App Store Connect MCP

App Store Connect MCP

by beautyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List user invitations

list-user-invitations
Read-onlyIdempotent

Retrieve pending user invitations for your App Store Connect team, with optional filters by email, role, or visible apps.

Instructions

Get a list of pending user invitations to your team

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": "list-user-invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of user invitations to return (default 100, max 200)
filter.emailNoFilter by invite email(s)
filter.rolesNoFilter by role(s)
filter.visibleAppsNoFilter by visible app ID(s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the context that the list contains 'pending' invitations and is scoped to 'your team', but it does not disclose pagination behavior, response format, or rate limits, so the added value beyond annotations is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that is front-loaded with the core information. There is no filler, repetition, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with comprehensive schema and annotations, the description is adequately complete. While there is no output schema, the tool's purpose is clear and the schema covers all inputs, so the lack of response details is not a significant gap.

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?

The input schema provides complete descriptions for all four parameters (100% coverage), so the description does not need to elaborate. The description adds no parameter-specific semantic information beyond what the schema already provides, warranting the baseline score.

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

Purpose5/5

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

The description clearly states the tool's action ('Get a list') and resource ('pending user invitations'), and scopes it to 'your team'. This distinguishes it from sibling tools like list-users, which retrieve existing users rather than invitations.

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?

The description provides no guidance on when to use this tool versus alternatives such as list-users or other invitation-related tools. It implies usage for pending invitations but does not explicitly mention exclusions or alternative tools.

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