Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_devices

Retrieve registered iOS and macOS devices for your App Store Connect team, with options to filter, sort, and limit results for efficient device management.

Instructions

Get a list of all devices registered to your team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of devices to return (default: 100, max: 200)
sortNoSort order for the results
filterNo
fieldsNo

Implementation Reference

  • The main handler function that implements the list_devices tool logic. It constructs query parameters from input args and calls the App Store Connect API endpoint '/devices'.
    async listDevices(args: {
      limit?: number;
      sort?: DeviceSortOptions;
      filter?: DeviceFilters;
      fields?: {
        devices?: DeviceFieldOptions[];
      };
    } = {}): Promise<ListDevicesResponse> {
      const { limit = 100, sort, filter, fields } = args;
      
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit)
      };
    
      if (sort) {
        params.sort = sort;
      }
    
      Object.assign(params, buildFilterParams(filter));
      Object.assign(params, buildFieldParams(fields));
    
      return this.client.get<ListDevicesResponse>('/devices', params);
    }
  • TypeScript interfaces and types defining the input parameters (filters, sort, fields) and output response structure (ListDevicesResponse) for the list_devices tool.
    export type DevicePlatform = "IOS" | "MAC_OS";
    export type DeviceStatus = "ENABLED" | "DISABLED";
    export type DeviceClass = "APPLE_WATCH" | "IPAD" | "IPHONE" | "IPOD" | "APPLE_TV" | "MAC";
    
    export interface Device {
      id: string;
      type: string;
      attributes: {
        name: string;
        platform: DevicePlatform;
        udid: string;
        deviceClass: DeviceClass;
        status: DeviceStatus;
        model?: string;
        addedDate?: string;
      };
    }
    
    export interface ListDevicesResponse {
      data: Device[];
    }
    
    export interface DeviceFilters {
      name?: string;
      platform?: DevicePlatform;
      status?: DeviceStatus;
      udid?: string;
      deviceClass?: DeviceClass;
    }
    
    export type DeviceSortOptions = 
      | "name" | "-name"
      | "platform" | "-platform"
      | "status" | "-status"
      | "udid" | "-udid"
      | "deviceClass" | "-deviceClass"
      | "model" | "-model"
      | "addedDate" | "-addedDate";
    
    export type DeviceFieldOptions = 
      | "name"
      | "platform"
      | "udid"
      | "deviceClass"
      | "status"
      | "model"
      | "addedDate";
  • src/index.ts:1380-1381 (registration)
    Registers the dispatch handler for the "list_devices" tool call, mapping it to the DeviceHandlers.listDevices method.
    case "list_devices":
      return { toolResult: await this.deviceHandlers.listDevices(args as any) };
  • src/index.ts:637-694 (registration)
    Tool registration in the listTools response, defining the name, description, and inputSchema for "list_devices".
      name: "list_devices",
      description: "Get a list of all devices registered to your team",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of devices to return (default: 100, max: 200)",
            minimum: 1,
            maximum: 200
          },
          sort: {
            type: "string",
            description: "Sort order for the results",
            enum: [
              "name", "-name", "platform", "-platform", "status", "-status",
              "udid", "-udid", "deviceClass", "-deviceClass", "model", "-model",
              "addedDate", "-addedDate"
            ]
          },
          filter: {
            type: "object",
            properties: {
              name: { type: "string", description: "Filter by device name" },
              platform: { 
                type: "string", 
                description: "Filter by platform",
                enum: ["IOS", "MAC_OS"]
              },
              status: { 
                type: "string", 
                description: "Filter by status",
                enum: ["ENABLED", "DISABLED"]
              },
              udid: { type: "string", description: "Filter by device UDID" },
              deviceClass: { 
                type: "string", 
                description: "Filter by device class",
                enum: ["APPLE_WATCH", "IPAD", "IPHONE", "IPOD", "APPLE_TV", "MAC"]
              }
            }
          },
          fields: {
            type: "object",
            properties: {
              devices: {
                type: "array",
                items: {
                  type: "string",
                  enum: ["name", "platform", "udid", "deviceClass", "status", "model", "addedDate"]
                },
                description: "Fields to include for each device"
              }
            }
          }
        }
      }
    },
  • The DeviceHandlers class constructor that receives the AppStoreConnectClient instance, used to instantiate the handler.
    import { sanitizeLimit, buildFilterParams, buildFieldParams } from '../utils/index.js';
    
    export class DeviceHandlers {
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get a list' implies a read-only operation, but it doesn't mention pagination behavior, rate limits, authentication requirements, or what happens when no devices exist. For a tool with 4 parameters and no annotation coverage, this is insufficient 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.

Conciseness5/5

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

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a listing operation and front-loads the essential information.

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 read-only listing tool with 4 parameters, no output schema, and no annotations, the description provides basic purpose but lacks important context about return format, pagination, error conditions, and relationship to sibling tools. It's minimally adequate but leaves significant gaps for an agent to use the tool effectively.

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 description mentions 'all devices' which implies no filtering by default, but doesn't explain the 4 available parameters (limit, sort, filter, fields). With 50% schema description coverage, the schema documents some parameters well but others minimally. The description adds little value beyond what the schema provides, meeting the baseline for moderate schema coverage.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('list of all devices registered to your team'), making the purpose immediately understandable. It doesn't distinguish from sibling tools (like 'list_apps' or 'list_users'), but it's specific enough to understand what the tool does without being tautological.

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. With multiple 'list_' sibling tools available (like list_apps, list_users, list_beta_groups), there's no indication of when this specific device listing tool is appropriate versus other listing operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/concavegit/app-store-connect-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server