Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_list_campaign_groups

Lists campaign groups for a LinkedIn ad account so you can review group structure and manage campaigns. Provide an account ID or rely on the current context.

Instructions

List campaign groups for a LinkedIn Ad Account.

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_campaign_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoThe ad account ID (uses context if not provided)

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 disclosure burden. It says nothing about read-only safety, whether results are paginated or truncated, what happens if account_id is missing beyond the schema hint, or whether an empty account returns an empty list.

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 short sentence that leads with the verb and resource; nothing is padded or redundant. Brevity is appropriate for a simple one-parameter list tool, though it borders on under-specification.

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 low-complexity list tool with full schema coverage and no output schema, the definition is minimally adequate. An agent can invoke it, but lacks context on result shape, pagination, and differentiation from sibling list tools.

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 the single account_id parameter is already documented including its context fallback, making 3 the baseline. The description adds no extra meaning such as accepted ID formats or account-scope semantics.

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 campaign groups") scoped to a LinkedIn Ad Account, which distinguishes it from linkedin_ads_list_campaigns and linkedin_ads_list_accounts by resource name. It stops short of explicitly contrasting with those siblings.

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 beyond the implicit reading of the name. The agent is not told how this differs from linkedin_ads_list_campaigns or when to prefer campaign-group vs campaign enumeration.

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