Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_list_campaigns

List LinkedIn ad campaigns for an ad account, with optional filters for status and campaign group to review active, paused, or other campaigns.

Instructions

List campaigns for a LinkedIn Ad Account, with optional status and campaign group filters.

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": "linkedin_ads_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status: ACTIVE, PAUSED, ARCHIVED, COMPLETED, CANCELED, DRAFT. Default: ACTIVE, PAUSED
account_idNoThe ad account ID
campaign_group_idNoFilter by campaign group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses little beyond the read-only implication of "List". It says nothing about pagination, result limits, ordering, or what a campaign record contains — all material for an agent deciding whether one call returns everything it needs.

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?

A single front-loaded sentence that scopes the resource before naming the filters; nothing is padded. It could be marginally stronger by leading with the key constraint, but there is no wasted wording.

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 three-parameter, no-annotation, no-output-schema tool, the definition covers the core action but omits operational context an agent would want: pagination/volume behavior, default result size, and any authentication or scope requirements. The rich schema compensates partially, keeping this at a minimum-viable level rather than inadequate.

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 all three parameters including the enumerated status values and the ACTIVE/PAUSED default are already documented in structured form. The description merely restates that status and campaign-group filters exist without adding semantics such as how multiple statuses combine or what happens when both filters are set.

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 states a specific verb and resource ("List campaigns for a LinkedIn Ad Account") and names the two filter dimensions, which is enough to distinguish it from siblings like linkedin_ads_list_accounts or linkedin_ads_list_campaign_groups. It stops short of explicitly contrasting itself with the performance/analytics siblings, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing tells the agent whether to reach for this instead of linkedin_ads_campaign_performance or linkedin_ads_analytics when the goal involves metrics. The only implicit routing is the word "campaigns", leaving the agent to infer the read-only inventory vs. reporting split.

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