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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

profiles_certificates_get_to_many_related

Fetch certificates linked to a provisioning profile by profile ID to inspect or manage signing assets. Supports paging and field selection for certificate details.

Instructions

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

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_certificates_get_to_many_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
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

C2/5.0
Behavior2/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. The 'GET' prefix at least implies a non-destructive read, but nothing is said about pagination behavior (despite a limit parameter), authentication/scopes, rate limits, or what the related-resource payload contains.

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 only content is the same URL printed twice inside parentheses, which is pure redundancy rather than front-loaded information. Every sentence should earn its place and this one does not.

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?

With no annotations, no output schema, and three parameters, the description should explain the paginated related-resource listing and how it differs from the relationship variant; instead it supplies only the raw endpoint. An agent cannot determine return shape, pagination, or the sibling distinction from the definition.

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 id, limit, and fields_certificates, and the baseline of 3 applies even though the description adds no parameter meaning of its own. The description contributes nothing about the sparse-fieldset or pagination semantics.

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 just the tool name restated as an HTTP route, duplicated in parentheses: "GET /v1/profiles/{id}/certificates (GET /v1/profiles/{id}/certificates)". It conveys the resource (certificates belonging to a profile) but adds no verb/resource explanation beyond the name itself, and does nothing to distinguish it from the sibling profiles_certificates_get_to_many_relationship, whose 'related' vs 'relationship' distinction is left entirely unexplained.

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 when-to-use guidance whatsoever. The description does not say when to call this instead of profiles_certificates_get_to_many_relationship, or any other certificate-listing tool such as certificates_get_collection or pass_type_ids_certificates_get_to_many_related.

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