Skip to main content
Glama
Hermoso

Hermoso

Official

List LinkedIn lead gen forms

list_linkedin_lead_forms
Read-onlyIdempotent

Retrieve LinkedIn lead gen forms owned by a Page or ad account, including IDs, names, states, versions, and requested fields. Inspect them before creating, editing, or archiving a form.

Instructions

The LEAD GEN FORMS a LinkedIn company Page or ad account owns — id, name, state, version and the fields each one asks for (firstName, email, company …). Make a new one with create_linkedin_lead_form; edit or archive one with update_linkedin_lead_form. If it answers that the connection must be reconnected, say exactly that: the lead-sync permission is granted at authorise time. Read-only, free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_linkedin_lead_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNothe company Page that owns the form — from list_linkedin_pages; omit when one Page is shared
adAccountIdNoread forms owned by an AD ACCOUNT instead of a Page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.209

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this while adding cost context ('free') and, more valuably, a behavioral rule for the authorise-time permission failure — information not derivable from any structured field. It does not discuss pagination or result limits, so it is strong but not exhaustive.

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?

Front-loads the resource and its return shape, then moves to sibling routing and finally the error-handling note. Every sentence carries information; only the trailing 'Read-only, free' partly restates the readOnlyHint annotation.

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?

With no output schema, the description usefully enumerates the returned fields, and it covers both parameters and the notable failure mode. For a simple two-optional-param list tool this is nearly sufficient; only pagination/volume expectations are absent.

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% with only two optional parameters, both already explained in the schema (pageId from list_linkedin_pages, adAccountId for ad-account ownership). The description's phrase 'a LinkedIn company Page or ad account owns' mirrors that but adds no new syntax, defaults, or precedence rules for when both are supplied.

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 the exact resource (LinkedIn lead gen forms owned by a Page or ad account) and enumerates the returned fields (id, name, state, version, field list), which cleanly separates it from lead-oriented siblings like list_linkedin_leads and get_linkedin_lead. It does not explicitly contrast itself with those siblings, but the resource specificity makes selection unambiguous.

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 explicit routing for adjacent operations: use create_linkedin_lead_form to make one, update_linkedin_lead_form to edit or archive. It also gives a concrete fallback instruction for the reconnect-permission failure. Missing is any statement of when NOT to use this versus list_linkedin_leads or list_linkedin_lead_subscriptions, so it stops short of full alternative coverage.

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