Skip to main content
Glama

ChatGPT Ads: send lead-form leads to the CRM

chatgpt_ads_lead_sync

Send a client's ChatGPT Ads lead-form responses (people who fill in the form inside ChatGPT) straight to their CRM: each lead becomes a HighLevel contact tagged chatgpt-ads-lead with the answers in a note, within seconds. Without HighLevel linked to the client, leads are kept and listed by chatgpt_ads_leads. Call without confirm to preview, then confirm: true. OpenAI switches lead forms on per ad account; if it isn't on yet, this says so.

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": {
      "account": "<account>"
    },
    "name": "chatgpt_ads_lead_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesThe ChatGPT Ads account: its client's name, the account name, or its adacct_ id (chatgpt_ads_list_accounts)
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Well beyond the annotations, the description states exactly what is created (a HighLevel contact tagged chatgpt-ads-lead with answers in a note), how fast it happens, and what occurs when no CRM is linked (leads are retained and listed by chatgpt_ads_leads). The preview semantics are also made explicit. The gap is that with idempotentHint=false, an agent is not told whether re-running the sync duplicates contacts, which is the main behavioral risk here.

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

Conciseness5/5

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

Four sentences, front-loaded with the outcome, then the no-CRM fallback, then the call procedure, then the prerequisite. The parenthetical gloss on lead forms is short and useful; nothing is redundant.

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?

There is no output schema, so the description carries the result story: contacts, tags, notes, timing, and the retained-leads fallback. That is nearly complete for a two-parameter sync tool. It falls slightly short on repeat-run/duplicate behavior and on what the preview output actually contains.

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 coverage is 100%, so both the account identifier forms and the confirm preview flag are already documented in the schema. The description restates the preview/confirm workflow without adding format, syntax, or selection detail beyond it. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description names a specific verb and object: it takes a client's ChatGPT Ads lead-form responses and writes each one into HighLevel as a tagged contact with a note. It also distinguishes the failure path by naming chatgpt_ads_leads as where leads land when no CRM is linked, so an agent can tell it apart from the sibling list/read tools.

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?

It gives a concrete two-step operating pattern: call without confirm to preview, then set confirm to true only after the user agrees. It also flags the prerequisite that OpenAI must have lead forms enabled on the ad account. It does not explicitly compare against nearby siblings such as prospects_to_highlevel or create_lead_form, so the routing is implied rather than spelled out.

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.