Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_list_predictive_audiences

Lists LinkedIn Predictive Audiences (lookalikes) for an ad account, returning parent DMP segment names, destinations, build status, location filters, seeds, and desired audience counts.

Instructions

List LinkedIn Predictive Audiences (lookalikes) in an ad account: each parent DMP segment with its name, destinations/build status, location filter, seeds and desiredAudienceCount. account_id is required (never taken from the working directory).

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_id": "<account_id>"
    },
    "name": "linkedin_ads_list_predictive_audiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesAd account id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does meaningful work: it discloses the return shape (parent DMP segment, name, destinations/build status, location filter, seeds, desiredAudienceCount) in the absence of an output schema, and it flags that account_id is required and never resolved from the working directory, which prevents a common invocation mistake. Gaps remain around pagination, permissions, and rate limiting, but the core behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence: verb and resource first, then the returned field inventory, then the required-parameter constraint. Every clause carries information an agent would otherwise have to guess, and nothing is repeated from the schema.

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?

For a single-parameter read tool with no output schema, the definition covers what it does, what comes back, and the key parameter constraint, which is nearly everything an agent needs. The remaining omission is how results are bounded (pagination or full-list behavior), which matters for large ad accounts.

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

Parameters5/5

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

Schema coverage is already 100% for the single parameter, so the baseline is 3; the description exceeds it by stating that account_id is mandatory and must be supplied explicitly rather than being inferred from the working directory. That adds real invocation semantics beyond the bare "Ad account id" schema text.

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 gives a specific verb and resource ("List LinkedIn Predictive Audiences (lookalikes) in an ad account") and even enumerates the returned fields, so the operation is unambiguous. It stops short of naming the sibling linkedin_ads_get_predictive_audience as the single-audience alternative, leaving the list-vs-get distinction to be inferred from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by "in an ad account" plus the note that account_id is required, which tells the agent this is a per-account enumeration call. There is no explicit when-to-use versus when-not guidance, no pointer to the single-audience getter, and no statement about pagination or result limits when an account has many audiences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.