Skip to main content
Glama

Honeyfield Marketing MCP

GA4: Manage Google ads links

ga4_manage_google_ads_links
Destructive

GA4 ↔ Google Ads verknüpfen (Conversions-Import + Audience-Export). action: list | create. property_id: die GA4-Property des Workspace (andere werden abgelehnt). create: customer_id muss das Google-Ads-Konto dieses Workspace sein (Bindestriche egal); andere werden abgelehnt, ohne konfiguriertes Ads-Konto scheitert der Aufruf. ads_personalization (Default true): personalisierte Werbung / Audience-Export erlauben. 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": {
      "action": "<action>",
      "property_id": "<property_id>"
    },
    "name": "ga4_manage_google_ads_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
workspaceNo
customer_idNo
property_idYes
ads_personalizationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's added value is the prerequisite disclosure: hard rejection of foreign property/customer IDs and failure without a configured Ads account, plus what ads_personalization actually controls. It stops short of describing re-link behavior or what happens to an existing link on create.

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

Conciseness4/5

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

Front-loads purpose and actions, then walks parameter-by-parameter with colon-delimited clauses — dense but every sentence carries a constraint or default. Slightly telegraphic and untranslated relative to the English tool name, but no filler.

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 all five parameters plus the key failure conditions are covered. The only gap is lifecycle detail for 'create' (idempotency, behavior when a link already exists), which matters for a destructive-flagged tool.

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

Parameters5/5

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

Schema coverage is 0% and the schema declares action as a bare string with no enum, so the description is the only place the valid values (list | create) appear. It also explains all four other parameters: property_id binding, customer_id format tolerance, ads_personalization default/effect, and workspace being optional when only one workspace exists.

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?

Names the concrete resource (GA4 ↔ Google Ads link) and the two supported operations (list, create), plus the side effects involved (conversion import, audience export). An agent can distinguish this from ga4_manage_audiences or the many ads_* tools without opening the schema.

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

Usage Guidelines4/5

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

Gives clear conditions per action: property_id must belong to the workspace ('andere werden abgelehnt'), customer_id must be this workspace's Ads account (hyphens ignored), and create fails outright if no Ads account is configured. It does not name explicit alternatives/exclusions (e.g. when to prefer ads_* account tools), which keeps it below a 5.

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