Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_integration_create

Create a Google Ads integration for a location by linking its location ID, ad account ID, and MCC ID through the ad publishing API.

Instructions

Create Google integration Create a Google Ads integration for a location Endpoint: POST /ad-publishing/google/integration (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

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": {
      "body": "<body>"
    },
    "name": "ghl_ad_google_integration_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateGoogleIntegrationDTO"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the safety bar is lower. The description adds genuinely useful context beyond them: the annotated POST endpoint with version header, and the required OAuth scope adPublishing.write. It does not explain what happens if an integration already exists for the location or whether any external OAuth handshake is triggered.

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

Conciseness3/5

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

The first two lines are near-duplicates ("Create Google integration" then a fuller restatement), which is wasteful given how short the description is. The endpoint and scope metadata are compact and useful, but the lead sentences should have been merged into one.

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

Completeness3/5

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

For a non-idempotent, open-world mutation with no output schema, the description covers the call mechanics and auth scope but leaves the outcome unspecified: whether an integration object is returned and how a duplicate-location case is handled. Adequate for invocation, incomplete for understanding consequences.

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%, and every nested body field (locationId, adAccountId, mccId) carries its own description and examples, so the schema does the heavy lifting. The description adds nothing about parameter meaning or formats beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Create a Google Ads integration for a location"), which distinguishes it from the Facebook and LinkedIn integration-create siblings and from the read-only ghl_ad_google_integration_get. It does not explicitly name the sibling it replaces, but the vendor specificity in the title plus the resource makes selection unambiguous.

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?

There is no explicit guidance on when to use this tool over alternatives, nor any note about prerequisites such as requiring the Google account to already be connected. The OAuth scope line hints at permissions but is not framed as a usage condition, so an agent must infer the correct context from the name alone.

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