workspace_resolve_conflict
Resolve a Google Tag Manager workspace entity merge conflict by supplying the resolved body and entity type; the tool wraps it in the required Entity envelope.
Instructions
Resolve a merge conflict for a workspace entity. You supply the resolved entity body plus its type; the GTM API wraps it in an Entity envelope ({ "tag": {...} } / { "trigger": {...} } / …), which this tool builds for you. NOTE: This is a complex operation — review the GTM UI conflict resolution first.
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": {
"accountId": "<accountId>",
"containerId": "<containerId>",
"workspaceId": "<workspaceId>",
"fingerprint": "<fingerprint>",
"entityType": "<entityType>",
"entityJson": "<entityJson>",
"confirm": "<confirm>"
},
"name": "workspace_resolve_conflict"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | Must be true to confirm this write operation. | |
| accountId | Yes | The GTM account ID. | |
| entityJson | Yes | JSON string of the RAW entity body (e.g. the tag object itself), NOT the Entity envelope — it is wrapped under entityType for you. If you pass an already-wrapped { "<entityType>": {...} } object it is used as-is. | |
| entityType | Yes | Which Entity slot the resolved body fills. The resolve_conflict API takes an Entity envelope, so a resolved tag is sent as { "tag": {...} }, a trigger as { "trigger": {...} }, etc. | |
| containerId | Yes | The GTM container ID. | |
| fingerprint | Yes | The workspace fingerprint at the time of conflict resolution. | |
| workspaceId | Yes | The GTM workspace ID. | |
| changeStatus | No | How the resolved entity changed relative to the base version (added/deleted/modified/none). Optional. |