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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_lead_form_list

Read-onlyIdempotent

Retrieve LinkedIn lead generation forms for an ad account, with optional field projection and pagination to fetch specific form data or page through full result sets.

Instructions

Get lead forms Retrieve LinkedIn lead gen forms for an ad account. By default each form is returned in full as a plain array; pass projection (comma-separated, dot-notation for nested fields) to return only the requested fields — any value outside the known field set is rejected. When limit is provided (max 100) the response is a paginated { leadForms, paging } envelope; pass pageToken (from paging.next) to fetch the next batch. Deprecated: use GET /ad-publishing/linkedin/accounts/{accountId}/forms with header version: v4. Endpoint: GET /ad-publishing/linkedin/{accountId}/forms (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly Pagination params: limit — pass them to page through full result sets.

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": {
      "accountId": "<accountId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_li_lead_form_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size for a paginated fetch (max 100). When set, the response is a { leadForms, paging } envelope instead of a plain array.
accountIdYesAccount identifier
pageTokenNoOpaque cursor for the next batch, taken from the previous response paging.next
locationIdYesLocation identifier
projectionNoFields to return on each lead form, comma-separated (e.g. ?projection=id,name,state,created,reviewInfo.reviewStatus). When set, only the requested fields are returned; any value outside the known field set is rejected. Nested fields use dot-notation (naming a parent like `reviewInfo` returns the whole object). Omit to receive the full form (including content.questions) as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100). When set, the response is a { leadForms, paging } envelope instead of a plain array.",
      +  "example": "100",
      +  "type": "string"
      +}
    • changedInput schema / properties / locationId / example
      Previous value: -"HChooFuiyPpVYzeJ4HMe"New value: +"loc_abc123"
    • addedInput schema / properties / pageToken
      Added value: +{
      +  "description": "Opaque cursor for the next batch, taken from the previous response paging.next",
      +  "example": "100",
      +  "type": "string"
      +}
    • addedInput schema / properties / projection
      Added value: +{
      +  "description": "Fields to return on each lead form, comma-separated (e.g. ?projection=id,name,state,created,reviewInfo.reviewStatus). When set, only the requested fields are returned; any value outside the known field set is rejected. Nested fields use dot-notation (naming a parent like `reviewInfo` returns the whole object). Omit to receive the full form (including content.questions) as-is.",
      +  "example": [
      +    "id",
      +    "name",
      +    "state",
      +    "created",
      +    "reviewInfo.reviewStatus"
      +  ],
      +  "items": {
      +    "enum": [
      +      "id",
      +      "name",
      +      "state",
      +      "created",
      +      "lastModified",
      +      "versionId",
      +      "creationLocale",
      +      "owner",
      +      "reviewInfo",
      +      "reviewInfo.reviewStatus",
      +      "reviewInfo.rejectionReasons",
      +      "content",
      +      "content.headline",
      +      "content.questions",
      +      "content.legalInfo",
      +      "hiddenFields"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observedv2.0.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the default response is a plain array but flips to a `{ leadForms, paging }` envelope when `limit` is set, the max page size is 100, unknown projection fields are rejected, and the required OAuth scope is adPublishing.readonly. It also discloses the API version header (v3) and deprecation status, which an agent cannot infer from 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?

The response-shape and pagination explanation is front-loaded and each of the first four sentences carries real information. The trailing line 'Pagination params: limit — pass them to page through full result sets' is a redundant template artifact that repeats the earlier limit/envelope explanation and slightly weakens the structure.

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, yet the description fully specifies the two possible return shapes (plain array vs paginated envelope) and how to page through results, so an agent knows exactly what it will receive. Combined with auth scope, endpoint version, and deprecation guidance, nothing material is missing for a read-only list tool.

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%, so the schema already documents all five parameters including the projection enum and dot-notation behavior. The description restates the projection/limit semantics and adds the useful hint that `pageToken` comes from `paging.next`, but adds no syntax or constraint details absent from the schema. Baseline 3 is appropriate.

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 and resource: 'Retrieve LinkedIn lead gen forms for an ad account,' which pins down both the platform (LinkedIn, not Facebook/Google) and the collection-level scope. It never explicitly names or contrasts a sibling (e.g. ghl_ad_li_lead_form_create or ghl_ad_fb_page_lead_form_list), so differentiation relies on the resource noun rather than an explicit routing statement.

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 clear operational context: omit `projection` to get the full form, pass `limit` to get the paginated envelope, use `pageToken` to continue. It also includes a genuine 'prefer instead' signal — 'Deprecated: use GET /ad-publishing/linkedin/accounts/{accountId}/forms with header version: v4' — which tells the agent when this endpoint is the wrong choice. No sibling-tool alternatives are mentioned.

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