Skip to main content
Glama

B2B Creators

by com.b2b-creators.mcp
OverviewDiscussionsAdmin

List ad campaigns

list_ad_campaigns
Read-onlyIdempotent

List the campaigns in a LinkedIn ad account with their objective, type and status. Use campaign ids to scope ads analysis to one campaign.

Input Schema

NameRequiredDescriptionDefault
profileNoOptional. An ads connection sessionId from list_profiles → adsConnections. Person names are ignored for ads: the workspace's shared LinkedIn Ads connection is used.
ad_account_idNoAd account id or name (partial name ok) from list_ad_accounts. Omit to use the first ad account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / ad_account_id / description
      Previous value: -"Ad account id from list_ad_accounts. Omit to use the first ad account."New value: +"Ad account id or name (partial name ok) from list_ad_accounts. Omit to use the first ad account."
    • changedInput schema / properties / profile / description
      Previous value: -"Profile name or sessionId from list_profiles."New value: +"Optional. An ads connection sessionId from list_profiles → adsConnections. Person names are ignored for ads: the workspace's shared LinkedIn Ads connection is used."
    • changedInput schema / properties / profile / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedInput schema / required
      Removed value: -[
-  "profile"
-]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safe-read profile is covered. The description adds useful context about which fields are returned, but omits any pagination or result-size behavior. Given annotation coverage, a 3 is appropriate.

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?

Two sentences, zero waste, with the core purpose front-loaded before the downstream-usage hint. Nothing is repeated or padded.

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 read-only list tool with full parameter coverage and no output schema, the description covers purpose, returned fields, and the id handoff to analysis tools. Minor gaps remain around pagination and result limits, but nothing essential to correct invocation is missing.

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 both parameters (profile, ad_account_id) are fully documented in the schema, including the shared-connection fallback and the 'omit to use first account' default. The description adds no parameter meaning beyond that, so baseline 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?

States a specific verb (List) and resource (campaigns in a LinkedIn ad account) and even names the returned fields (objective, type, status). It is distinguishable from list_ad_accounts and list_company_posts, but does not explicitly contrast with the closest sibling get_ad_creatives or get_ads_performance.

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 second sentence implies usage by explaining that campaign ids let the agent scope ads analysis to one campaign, which links it to the performance siblings. However there is no explicit when-to-use versus list_ad_accounts, and no exclusion or prerequisite stated.

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

All B2B Creators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources