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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

nominations_get_collection

Retrieve App Store nominations with filtering, sorting, and relationship includes to review submission states, types, and related apps or events.

Instructions

GET /v1/nominations (GET /v1/nominations)

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": "nominations_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
fields_appsNothe fields to include for returned resources of type apps
filter_typeNofilter by attribute 'type'
filter_stateNofilter by attribute 'state'
fields_actorsNothe fields to include for returned resources of type actors
fields_appEventsNothe fields to include for returned resources of type appEvents
limit_inAppEventsNomaximum number of related inAppEvents returned (when they are included)
limit_relatedAppsNomaximum number of related relatedApps returned (when they are included)
fields_nominationsNothe fields to include for returned resources of type nominations
fields_territoriesNothe fields to include for returned resources of type territories
filter_relatedAppsNofilter by id(s) of related 'relatedApps'
filter_hasInAppEventsNofilter by attribute 'hasInAppEvents'
limit_supportedTerritoriesNomaximum number of related supportedTerritories returned (when they are included)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.4/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. It says nothing about pagination, read-only semantics, auth requirements, rate limits, or what a collection response looks like — only a bare HTTP 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?

It is short, but the brevity is under-specification rather than conciseness: the same endpoint string is duplicated in parentheses, and no useful information is front-loaded because there is none.

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 a 15-parameter collection endpoint with no annotations and no output schema, the description is completely inadequate — an agent has no idea what a nomination is, what the collection returns, or how the many filter/include/field parameters relate to the result.

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 15 parameters (sort, limit, include, fields_*, filters, limits), so the schema already documents every parameter. The description adds nothing, but the baseline of 3 applies when the schema does the heavy lifting.

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

Purpose1/5

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

The description is only 'GET /v1/nominations (GET /v1/nominations)' — a raw endpoint restated twice. It conveys no more meaning than the tool name already does and gives no verb+resource framing beyond 'GET'.

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 collection endpoint versus siblings such as nominations_get_instance or nominations_create_instance, nor any 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