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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

merchant_ids_get_collection

Retrieves merchant IDs from App Store Connect, with options to filter by name or identifier, sort results, and include related certificates.

Instructions

GET /v1/merchantIds (GET /v1/merchantIds)

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

Input Schema

NameRequiredDescriptionDefault
sortNocomma-separated list of sort expressions; resources will be sorted as specified
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
filter_nameNofilter by attribute 'name'
filter_identifierNofilter by attribute 'identifier'
fields_merchantIdsNothe fields to include for returned resources of type merchantIds
limit_certificatesNomaximum number of related certificates returned (when they are included)
fields_certificatesNothe fields to include for returned resources of type certificates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

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 behavioral burden, and it discloses nothing. It does not say whether results are paginated, whether authentication/permissions are required, or what happens with large collections — all of which matter for a collection endpoint with a limit parameter.

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 the brevity comes from under-specification rather than efficiency — the same route string is duplicated in parentheses, which is pure waste with no informational content.

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 8-parameter collection endpoint with pagination, relationship inclusion, filtering, and sparse fieldsets, and with no output schema to fall back on, a duplicated URL path is completely inadequate. An agent cannot tell what this tool yields or how to shape the query.

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%, so the schema already documents all 8 optional parameters (sort, limit, include, filters, sparse fieldsets). Per the baseline rule, 3 is the ceiling when the schema does the heavy lifting, and the description adds no parameter meaning whatsoever on top of it.

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 route echoed twice: 'GET /v1/merchantIds (GET /v1/merchantIds)'. It restates the tool name and HTTP verb rather than describing what a merchant ID resource is or what the collection returns, which is a tautology rather than a statement of 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 indication of when to use this collection endpoint versus siblings such as merchant_ids_get_instance (single lookup) or merchant_ids_certificates_get_to_many_related. The agent is given no conditions, prerequisites, or alternatives.

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