Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_get_predictive_audience

Retrieve a LinkedIn Predictive Audience by parent DMP segment ID to inspect its name, account, destinations, targeting filters, seeds, desired audience count, and version tag.

Instructions

Get one LinkedIn Predictive Audience by its parent DMP segment id: name, account, destinations (build status, size), targetingFilter (locations), seeds, desiredAudienceCount and versionTag.

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": {
      "dmp_segment_id": "<dmp_segment_id>"
    },
    "name": "linkedin_ads_get_predictive_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
dmp_segment_idYesParent DMP segment id (the id shown by list_predictive_audiences)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It partially compensates by enumerating the returned fields (name, account, destinations with build status and size, targetingFilter locations, seeds, desiredAudienceCount, versionTag), which is genuinely useful with no output schema, but it says nothing about permissions, error behavior when the segment is missing, or whether build status can be transient.

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?

It is a single front-loaded sentence with the identifying key placed before the field list, and no filler. The dense parenthetical field enumeration is informative but slightly heavy for one sentence.

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 one-parameter read-only lookup with no output schema, the description covers both the input key and the shape of the returned payload, which is most of what an agent needs. It leaves minor gaps around failure modes and the meaning of the build status values.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that it is the parent DMP segment id shown by list_predictive_audiences. The description only restates this ('by its parent DMP segment id') without adding format or sourcing detail, so the baseline of 3 applies.

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 uses a specific verb and resource ('Get one LinkedIn Predictive Audience') and names the key that identifies it (parent DMP segment id), so it is clearly a single-item lookup rather than a list. It does not explicitly name linkedin_ads_list_predictive_audiences as the alternative, so it falls short of the top score.

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?

The phrase 'Get one ... by its parent DMP segment id' implies a retrieval-by-identifier workflow, which is adequate usage context. However, there is no explicit statement of when to choose this over listing audiences or how to obtain the id within the description itself.

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