Skip to main content
Glama

ChatGPT Ads: leads from lead forms

chatgpt_ads_leads
Read-onlyIdempotent

The leads a client got from ChatGPT Ads lead forms: name, email, phone, answers, when, and whether each reached the CRM.

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_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
accountYesThe ChatGPT Ads account: its client's name, the account name, or its adacct_ id (chatgpt_ads_list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by disclosing the returned fields (including CRM-reached status), which is useful since no output schema exists. It says nothing about volume, pagination, or how the default window behaves, so it does not go far beyond the annotations.

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?

A single economical sentence with the core resource front-loaded and the field list as a compact tail. Nothing is redundant, though it is a fragment rather than a structured statement of action and scope.

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 simple two-parameter read tool the description covers what the caller gets back, which is valuable in the absence of an output schema. It omits the unstated 'days' semantics, result limits, and any routing guidance relative to the lead-sync sibling, leaving the agent to infer query scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'account' is well documented in the schema (client name, account name, or adacct_ id), but 'days' has no description at all beyond min/max/default 30. The description never mentions either parameter, so it does not compensate for the 'days' gap or clarify that it is a lookback window.

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?

Names a specific resource (leads from ChatGPT Ads lead forms) and enumerates what each record contains (name, email, phone, answers, timestamp, CRM status). An agent can tell this apart from form-management or sync tools from the content alone. It lacks an explicit verb and never names the sibling it differs from, so it stops short of a 5.

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 statement of when to use this versus chatgpt_ads_lead_sync or lead_forms, and no prerequisite or exclusion is given. Usage is only implied by the noun phrase 'the leads a client got'. Given several closely related lead siblings, this is a meaningful gap.

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.