Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

territories__list

Read-onlyIdempotent

Retrieve a list of App Store territories with optional pagination and field selection. Use this to get available territories for sales, pricing, or reporting.

Instructions

List territories. [GET /v1/territories]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomaximum resources per page
next_urlNoAbsolute links.next URL from a previous response.
fields_territoriesNothe fields to include for returned resources of type territories Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / fields_territories
      Added value: +{
+  "description": "the fields to include for returned resources of type territories Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "currency"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / next_url / description
      Previous value: -"Absolute `links.next` URL from a previous response, to fetch the next page. When set, all other parameters are ignored."New value: +"Absolute links.next URL from a previous response."
  2. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds no behavioral details beyond what the annotations already provide. It doesn't mention pagination behavior, return format, or any constraints, so its value over the readOnlyHint/idempotentHint is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely compact, using two short segments to convey the basic purpose and endpoint. Every word is functional, with no fluff.

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?

For a list tool, the description is underspecified. It fails to clarify global vs. scoped territory listing, pagination via next_url, or the optional fields_territories behavior. The sibling tools that also list territories make this ambiguity more impactful.

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?

The schema already documents all three parameters with full coverage, so the description doesn't need to add parameter details. It adds no semantic context beyond the schema, but it doesn't mislead either.

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

Purpose4/5

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

The description clearly states the action ('List territories') and includes the HTTP endpoint, making the tool's function identifiable. However, it doesn't specify that this is the global list, which could be confused with sibling tools like 'app_tags__territories__list' or 'end_user_license_agreements__territories__list'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the sibling territory-listing tools. The description only restates the operation and endpoint, leaving the agent to guess the appropriate context.

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