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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apps_app_clips_get_to_many_related

Retrieve App Clips associated with a specific app ID, with pagination and optional related experiences or fields.

Instructions

GET /v1/apps/{id}/appClips (GET /v1/apps/{id}/appClips)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
fields_appsNothe fields to include for returned resources of type apps
fields_appClipsNothe fields to include for returned resources of type appClips
filter_bundleIdNofilter by attribute 'bundleId'
limit_appClipDefaultExperiencesNomaximum number of related appClipDefaultExperiences returned (when they are included)
fields_appClipDefaultExperiencesNothe fields to include for returned resources of type appClipDefaultExperiences

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 burden, and it discloses nothing: not that this is a read-only paginated list, not the pagination mechanics (limit), not that filters/field selection shrink the payload. Only the word GET weakly implies read-only.

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 it is vacuous rather than concise: the single sentence is the raw route echoed twice, so no sentence contributes information an agent could act on.

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 eight-parameter list endpoint with no annotations and no output schema, the description should explain the returned collection and the effect of include/fields/limit. It does none of this, leaving the definition materially incomplete.

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 all eight parameters (id, limit, include, fields_*, filter_bundleId, limit_appClipDefaultExperiences) are documented in the schema itself. The description adds zero parameter meaning beyond that, so the baseline 3 applies.

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 a verbatim restatement of the HTTP path ("GET /v1/apps/{id}/appClips"), duplicated twice. It conveys that appClips are retrieved for an app id, but it is tautological rather than a plain-language statement of purpose and offers nothing to distinguish it from siblings like apps_app_clips_get_to_many_relationship.

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?

No guidance whatsoever on when to use this tool versus the closely named apps_app_clips_get_to_many_relationship, app_clips_get_instance, or app_clips_app_clip_default_experiences_get_to_many_related. The agent is left to infer everything from the identifier.

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