Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by chimpmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_google_ads_links

Retrieve links to Google Ads accounts linked to a specified GA4 property. Enables viewing associated advertising accounts for integrated reporting.

Instructions

Returns a list of links to Google Ads accounts for a GA4 property.

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

Input Schema

NameRequiredDescriptionDefault
property_idYesGA4 property ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are not provided, so the description is the sole source. It indicates a read-only operation ('Returns a list'), but does not disclose any potential side effects, rate limits, or scope limitations beyond the GA4 property. It is minimally transparent.

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, concise sentence that effectively communicates the tool's purpose. There is no redundant or irrelevant information; every word earns its place.

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 list tool with one parameter and no output schema, the description adequately conveys the return value ('list of links'). However, it does not specify the structure of each link (e.g., URL, account name), which would be helpful for an agent to interpret the result.

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% for the single parameter 'property_id', which already documents itself as 'GA4 property ID'. The description does not add any additional meaning or constraints beyond what the schema provides.

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 the tool returns a list of links to Google Ads accounts for a GA4 property. It uses a specific verb ('Returns') and resource ('list of links'), and distinguishes itself from sibling tools like get_account_summaries or run_report by focusing on Google Ads linking.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when-not-to-use, or sibling tools that might be more appropriate for related tasks.

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