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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

profiles_devices_get_to_many_related

Retrieve all devices tied to a provisioning profile ID. Use it to manage device lists for app provisioning, testing, and distribution.

Instructions

GET /v1/profiles/{id}/devices (GET /v1/profiles/{id}/devices)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
fields_devicesNothe fields to include for returned resources of type devices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/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 entire burden of behavioral disclosure, and it discloses nothing: no note about it being a safe read, no pagination behaviour despite a 'limit' parameter, no indication of what the relationship returns. A bare URL tells the agent nothing beyond verb and path.

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 its brevity is under-specification rather than economy: the same route is printed twice with no added information in the parenthetical. There is no front-loaded explanation and no useful structure.

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

Completeness2/5

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

For a simple GET-to-many relationship with full schema coverage this could be minimally viable, but with no annotations, no output schema, and a description consisting only of a duplicated URL, the agent has no confirmation of what is returned or how the pages work. More context is needed even for a simple read tool.

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% – id, limit and fields_devices are each documented in the schema – so the baseline of 3 applies. The description adds no meaning of its own, but the schema already does the heavy lifting for these three parameters.

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 nothing but the HTTP route 'GET /v1/profiles/{id}/devices', duplicated in parentheses. It restates the tool name (profiles_devices_get_to_many_related) rather than explaining in plain language that it lists the devices associated with a profile. An agent can guess the resource from the URL, but this is tautology rather than a stated purpose.

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 tool, no prerequisites, and no mention of alternatives. Siblings such as profiles_devices_get_to_many_relationship or devices_get_collection exist, and nothing here helps an agent choose between them.

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