Skip to main content
Glama

Link a GA4 property

set_ga4_property
DestructiveIdempotent

Links a Google Analytics 4 property to one Search Console property in Organiq (the same setting as the panel's "Integrações" block): ga4PropertyId is the numeric id from list_ga4_properties ("123456789" or "properties/123456789"); null unlinks. Returns the property settings. When the value changes, the GA4 data already synced from the previous property is deleted and the next daily sync rebuilds the history from the new one (Search Console data is untouched); get_ai_traffic answers after that sync. Needs the write scope (mcp:write). Use it when check_connection lists no_ga4 or the user asks to connect GA4. Guide: https://organiqgeo.com/connect/ga4. / Liga a propriedade GA4 à propriedade do Search Console; trocar apaga o GA4 já sincronizado e o sync refaz.

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": {
      "site": "<site>",
      "ga4PropertyId": "<ga4PropertyId>"
    },
    "name": "set_ga4_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesProperty: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.
ga4PropertyIdYesNumeric GA4 property id ("123456789" or "properties/123456789"), from list_ga4_properties; null unlinks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. / Propriedade por nome, siteUrl ou id."New value: +"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. The value \"demo\" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; \"demo\" é um site de demonstração com dados fictícios, sem login e só leitura."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the concrete cost: synced GA4 data from the previous property is deleted and rebuilt by the next daily sync, while Search Console data is untouched. It also states the mcp:write scope requirement and the downstream effect on get_ai_traffic, which is exactly the context annotations cannot convey.

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?

The English text is well front-loaded: destination, parameter meaning, destructive effect, prerequisite check, then link. The trailing Portuguese sentence duplicates the linking and data-loss points verbatim, which is a real redundancy rather than a structural flaw.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the definition covers everything an agent needs: identifier source, unlink path, required scope, data-loss consequences, and how to confirm readiness. It even notes that return value is the property settings.

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%, so both parameters are already documented with formats and the null-unlink behavior. The description repeats the accepted id formats and points to list_ga4_properties as the source, which is mildly useful but adds no syntax or constraint beyond the schema; baseline 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?

States a specific verb and resource: links a GA4 property to one Search Console property in Organiq, and also discloses the inverse (null unlinks). It pins the tool's identity to the panel's "Integrações" block, so an agent can distinguish it from read-only siblings like list_ga4_properties or get_ai_traffic.

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

Usage Guidelines5/5

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

Gives an explicit trigger: use it when check_connection reports no_ga4 or the user asks to connect GA4. It also names the prerequisite source for the identifier (list_ga4_properties) and the required scope, leaving no inference needed about when this tool is the right call.

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.