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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_clip_header_images_get_instance

Retrieve an App Clip header image by ID, with optional related localization data and selected fields, to inspect its metadata, upload state, or asset details.

Instructions

GET /v1/appClipHeaderImages/{id} (GET /v1/appClipHeaderImages/{id})

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_appClipHeaderImagesNothe fields to include for returned resources of type appClipHeaderImages
fields_appClipDefaultExperienceLocalizationsNothe fields to include for returned resources of type appClipDefaultExperienceLocalizations

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 state that this is a read-only operation, whether authentication is required, what happens if the id is missing or unauthorized, or anything about the response shape.

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 same path string is repeated twice inside parentheses, which is pure noise rather than front-loaded meaning. Brevity here reflects under-specification, not efficiency.

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?

With no annotations, no output schema, and four parameters, the description should explain at minimum what the tool returns and any access constraints. Instead it supplies only a raw endpoint path, leaving the agent with no behavioral or contextual grounding for invocation.

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%, with the schema documenting id, include, and both fields_* sparse-fieldset parameters, so the baseline is 3. The description adds no syntax, format, or constraint details beyond what the schema already states.

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 only a REST path, 'GET /v1/appClipHeaderImages/{id}', duplicated verbatim in parentheses. It restates the tool name rather than describing the action in natural language, though the path does imply a single-resource fetch by id. This is effectively a tautology with no distinguishing detail from siblings like app_clip_header_images_update_instance.

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 versus alternatives, no prerequisites, and no indication of when not to use it. An agent gets nothing about how this single-fetch differs from create/update/delete siblings on the same resource.

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