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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_targeting_search

Read-onlyIdempotent

Search LinkedIn ad targeting facets such as locations, industries, and job titles to identify audience criteria for GoHighLevel ad campaigns.

Instructions

Search targeting options Search LinkedIn targeting facets such as locations, industries, and job titles Endpoint: GET /ad-publishing/linkedin/targeting/search (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": {
      "locationId": "<locationId>",
      "facet": "<facet>"
    },
    "name": "ghl_ad_li_targeting_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoQuery parameter
facetYesTargeting facet
queryNoSearch query
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is read-only, idempotent, open-world, and non-destructive. The description adds operational context beyond that, including the GET endpoint, v3 version header, and the required adPublishing.readonly OAuth scope.

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 description is short and front-loaded, with the core purpose stated early. The first line slightly duplicates the title, but the endpoint and OAuth scope lines carry useful metadata without bloating the definition.

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 search tool with no output schema, the description does not explain the response shape, pagination behavior, or result limits. It is adequate for invocation but leaves gaps around what the agent should expect to receive.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful examples for the facet parameter ('locations, industries, and job titles') that help interpret the required facet value beyond the generic schema label 'Targeting facet.'

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 gives a specific verb and resource: 'Search LinkedIn targeting facets such as locations, industries, and job titles.' It clearly distinguishes this tool from the Facebook and Google targeting-search siblings by naming LinkedIn explicitly.

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?

The description supplies clear usage context: it is for searching LinkedIn targeting facets used in ad targeting. It does not explicitly state when not to use it or name alternatives, but the LinkedIn-specific scope makes the intended use clear.

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