Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

analytics_reports__get

Read-onlyIdempotent

Retrieve a specific analytics report by ID to access detailed app performance metrics, enabling targeted analysis of your app's data.

Instructions

Read one analytics report by ID. [GET /v1/analyticsReports/{id}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID from the matching list call.
fields_analyticsReportsNothe fields to include for returned resources of type analyticsReports Return only these attributes. A full row set can exceed 200 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / id / description
      Added value: +"ID from the matching list call."
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / fields_analyticsReports
      Added value: +{
+  "description": "the fields to include for returned resources of type analyticsReports Return only these attributes. A full row set can exceed 200 KB.",
+  "items": {
+    "enum": [
+      "name",
+      "category",
+      "instances"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / id / description
      Removed value: -"Resource identifier."
  3. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the HTTP endpoint but no additional behavioral details like return format, pagination, or rate limits. With annotations present, a 3 is appropriate as it does not contradict and adds minimal context.

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 a single sentence with the key action and endpoint, zero waste. It is front-loaded and immediately comprehensible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get-by-ID tool with complete schema coverage and safety annotations, the description is sufficient. The lack of an output schema is mitigated by the straightforward purpose, though a bit more detail on return values could enhance completeness.

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%, and both parameters ('id' and 'fields_analyticsReports') have clear descriptions. The tool description itself adds no extra semantic value beyond the schema, so the baseline score of 3 applies.

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

Purpose5/5

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

The description clearly states 'Read one analytics report by ID' with a specific verb ('Read'), resource ('analytics report'), and scope ('by ID'). This distinguishes it from sibling list tools like analytics_reports__instances__list. The endpoint reference adds clarity.

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

Usage Guidelines3/5

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

The description implies usage through 'by ID' but does not explicitly state when to use this vs alternatives. It lacks guidance on when not to use it (e.g., when needing multiple reports) or mention of related list/get siblings. The prerequisite of having an ID from a list call is only in the schema, not the description.

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