app-store-connect-mcp

Overview Schema Source Related Servers Discussions Admin

beta_testers_get_collection

Retrieve and filter App Store Connect beta testers by name, email, invite type, state, app, build, or beta group, with sorting, pagination, and relationship includes.

Instructions

GET /v1/betaTesters (GET /v1/betaTesters)

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": "beta_testers_get_collection"
  }
}

Input Schema

Name	Required	Description
`sort`	No	comma-separated list of sort expressions; resources will be sorted as specified
`limit`	No	maximum resources per page
`include`	No	comma-separated list of relationships to include
`filter_id`	No	filter by id(s)
`limit_apps`	No	maximum number of related apps returned (when they are included)
`fields_apps`	No	the fields to include for returned resources of type apps
`filter_apps`	No	filter by id(s) of related 'apps'
`filter_email`	No	filter by attribute 'email'
`limit_builds`	No	maximum number of related builds returned (when they are included)
`fields_builds`	No	the fields to include for returned resources of type builds
`filter_builds`	No	filter by id(s) of related 'builds'
`filter_lastName`	No	filter by attribute 'lastName'
`filter_firstName`	No	filter by attribute 'firstName'
`limit_betaGroups`	No	maximum number of related betaGroups returned (when they are included)
`fields_betaGroups`	No	the fields to include for returned resources of type betaGroups
`filter_betaGroups`	No	filter by id(s) of related 'betaGroups'
`filter_inviteType`	No	filter by attribute 'inviteType'
`fields_betaTesters`	No	the fields to include for returned resources of type betaTesters

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Oct 21, 2026

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, and it discloses nothing — no pagination behavior, no auth requirements, no indication that results are a filtered/sorted list. A raw endpoint echo is not behavioral context.

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 this is under-specification rather than conciseness — the single line repeats the same path twice and front-loads nothing useful. Every sentence should earn its place, and neither copy does.

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 an 18-parameter collection endpoint with no output schema and no annotations, the description is completely inadequate. It leaves the agent to infer the resource type, the meaning of the collection semantics, and any pagination or filtering context entirely from the tool name.

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% across all 18 parameters (sort, limit, include, filter_*, fields_*, limit_*), so the schema already documents each one; the description adds nothing beyond it. Per the high-coverage baseline, 3 is the correct score.

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 is just the HTTP endpoint restated twice: 'GET /v1/betaTesters (GET /v1/betaTesters)'. It conveys no verb-plus-resource statement in natural language and does nothing to distinguish this collection fetch from siblings like beta_testers_get_instance or beta_groups_beta_testers_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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent receives zero help deciding between this tool and the many other beta-tester retrieval tools in the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server