Skip to main content
Glama

Honeyfield Marketing MCP

GA4: List custom metrics

ga4_list_custom_metrics
Read-only

Custom Metrics einer GA4 Property auflisten (Name, Parameter, Einheit, Scope). property_id: die GA4-Property des Workspace (andere werden abgelehnt). workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "property_id": "<property_id>"
    },
    "name": "ga4_list_custom_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
property_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact – foreign property IDs are rejected – but says nothing about pagination, empty results, or rate limits, so it only modestly exceeds the annotation baseline.

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?

Three short lines: purpose first, then one line per parameter, zero filler. Every sentence carries information an agent needs.

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?

With an output schema present, return values need no explanation, and both parameters plus the safety profile are covered. Only minor gaps remain (property_id format, list-size/pagination behavior), which are not blocking for a simple read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does: property_id is defined as the workspace's GA4 property with a rejection rule, and workspace is defined as the customer-workspace slug with an optionality condition. It only omits the expected string format for property_id (e.g. 'properties/123').

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?

States a specific verb (auflisten) and resource (Custom Metrics of a GA4 property) and even enumerates the returned fields (Name, Parameter, Einheit, Scope). This clearly distinguishes it from ga4_list_custom_dimensions, ga4_create_custom_metric and ga4_archive_custom_metric.

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 gives a real constraint (property_id must belong to the workspace, other properties are rejected) and notes workspace is optional when only one exists. However, it never says explicitly when to reach for this tool versus the sibling list/create/archive tools, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources