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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_segment_offline_job_create

Create an offline user list job to upload CSV or smart-list users to a Google Customer Match list for ad targeting.

Instructions

Create offline user list job Create a job to upload users to a Google customer match list Endpoint: POST /ad-publishing/google/segments/offline-user-list-job (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_segment_offline_job_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: +"CreateOfflineUserListJobDTO"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true. The description adds the concrete endpoint and the required OAuth scope (adPublishing.write), which is genuinely useful context. However, it says nothing about the asynchronous job lifecycle — whether a job ID is returned, whether it must be polled, or whether repeated non-idempotent calls queue duplicate uploads.

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 core statement is front-loaded and unambiguous, followed by a short clarifying sentence and three compact metadata lines. No sentence is wasted, though the 'source: v3/ad-publishing-v3.json' fragment is spec provenance that an agent gains little from.

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?

There is no output schema, so the description must carry the response burden — and it omits what a successful call returns (job identifier, status) and how progress is then tracked, even though a sibling (ghl_ad_google_get_publishing_progress) suggests an async workflow. For a nested-object write tool, this is an adequate but incomplete definition.

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%: every field in the nested CreateOfflineUserListJobDTO (csvPath, isDynamic, locationId, userListId, smartListIds) carries its own description and example. The prose adds no further meaning 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 opens with a specific verb+resource ('Create offline user list job') and immediately clarifies the business purpose: uploading users to a Google customer match list. That distinguishes it from siblings like ghl_ad_google_segment_upsert or ghl_ad_google_segment_list, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the stated purpose — an agent can infer this is the tool for pushing a CSV/smart-list audience into Google Customer Match. There is no guidance on when to prefer this over segment_upsert, no prerequisites beyond the OAuth scope, and no mention of what must exist first (userListId, csvPath upload).

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