Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

beta_recruitment_criterion_options__list

Read-onlyIdempotent

List available beta recruitment criterion options for App Store Connect, including device family and OS version attributes. Use this to retrieve paginated criteria for configuring beta testing.

Instructions

List beta recruitment criterion options. [GET /v1/betaRecruitmentCriterionOptions]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomaximum resources per page
next_urlNoAbsolute links.next URL from a previous response.
fields_betaRecruitmentCriterionOptionsNothe fields to include for returned resources of type betaRecruitmentCriterionOptions Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / fields_betaRecruitmentCriterionOptions
      Added value: +{
+  "description": "the fields to include for returned resources of type betaRecruitmentCriterionOptions Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "deviceFamilyOsVersions"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / next_url / description
      Previous value: -"Absolute `links.next` URL from a previous response, to fetch the next page. When set, all other parameters are ignored."New value: +"Absolute links.next URL from a previous response."
  2. First observedv1.3.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description merely restates 'List' and gives the HTTP endpoint, adding no behavioral context beyond what annotations and the tool name already convey. It does not mention pagination, response size caveats, or filtering nuances.

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 sentence that states the action and includes the endpoint. It is extremely concise, front-loaded, and contains zero wasted words.

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

Completeness3/5

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

For a simple read-only list tool with well-documented parameters and safety annotations, the description is minimally adequate. However, with no output schema, it does not describe what the returned options look like or how they are used, leaving some ambiguity for an agent unfamiliar with beta recruitment.

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 meaningful descriptions for limit, next_url, and fields. The description adds no additional parameter meaning, so the baseline 3 applies because the schema carries the semantics fully.

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 uses a specific verb ('List') and resource ('beta recruitment criterion options'), and includes the exact endpoint path. This clearly distinguishes it from sibling tools like beta_recruitment_criteria__create or beta_groups__beta_recruitment_criteria__get.

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

Usage Guidelines3/5

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

The description clearly implies this is for listing beta recruitment criterion options, but it does not explicitly state when to use it versus alternatives or provide exclusions. For a simple list resource, the context is understandable but not fully spelled out.

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