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

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_lead_form_get

Read-onlyIdempotent

Retrieve a Facebook lead form by ID, including its published Meta definition, or set isDraft=true to fetch an unpublished local draft instead.

Instructions

Get lead form by ID Retrieve a lead form by id. Pass isDraft=true to read an unpublished local draft instead, in which case leadFormId accepts either the bare id or the draft_-prefixed form the listing endpoint reports. The two branches return different shapes, and neither matches the shape the listing endpoint returns for the same form: the published branch carries the full Meta definition (context card, thank-you page, legal content) but no status, createdTime, or pageId, while the draft branch returns the stored document verbatim under _id. Endpoint: GET /ad-publishing/facebook/lead-form/{leadFormId} (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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": {
      "leadFormId": "<leadFormId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_fb_lead_form_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
isDraftNoFetch the unpublished draft of this lead form instead of the published form
leadFormIdYesLead form identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / isDraft / description
      Previous value: -"Is draft"New value: +"Fetch the unpublished draft of this lead form instead of the published form"
  2. First observedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial non-obvious behavior: the two branches return different shapes, neither matches the listing shape, the published branch omits status/createdTime/pageId, and the draft returns the stored document verbatim under _id. Endpoint path, version header, and the required adPublishing.readonly scope are also disclosed.

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?

Purpose is front-loaded in the first clause, then branch semantics, then endpoint/scope metadata. The return-shape sentence is dense but every clause carries usable information; only the endpoint boilerplate is close to filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by characterizing what each branch returns. With OAuth scope, endpoint, and both parameter behaviors covered, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining that isDraft switches the read branch and that leadFormId accepts either the bare id or the draft_-prefixed form reported by the listing endpoint.

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?

States a specific verb and resource ('Retrieve a lead form by id') and immediately separates the two retrieval branches (published vs. isDraft draft). It also explicitly distinguishes the result from what the listing endpoint returns, so an agent can tell get-by-id apart from the sibling list/create tools without opening a schema.

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?

Gives a concrete trigger for the non-default path ('Pass isDraft=true to read an unpublished local draft') and explains the accepted id forms. It does not name sibling alternatives or list exclusions, but the get-vs-list/create split is implied clearly enough.

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