Skip to main content
Glama

B2B Creators

by com.b2b-creators.mcp
OverviewDiscussionsAdmin

List individual ads (creatives)

get_ad_creatives
Read-onlyIdempotent

List the individual ads in a LinkedIn ad account: copy, headline, format, status, campaign and whether it is a Thought Leadership ad. Pair with get_ad_performance_breakdown to see how each one performed.

Input Schema

NameRequiredDescriptionDefault
limitNoMax ads to return. Defaults to 40.
profileNoOptional. An ads connection sessionId from list_profiles → adsConnections. Person names are ignored for ads: the workspace's shared LinkedIn Ads connection is used.
campaign_idsNoOptional campaign ids from list_ad_campaigns to narrow the list.
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

A4/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 safety profile is covered. The description usefully adds the composition of the returned creatives (copy, headline, format, status, Thought Leadership flag), but says nothing about pagination behavior, result ordering, or auth requirements beyond what annotations imply.

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: the first front-loads what the tool returns, the second gives the pairing recommendation. Well-sized for a list tool.

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?

With no output schema, the description compensates by naming the key fields returned, and annotations cover the safety profile. It is complete enough to call correctly, though it omits result count/pagination context that an agent might want for a list endpoint.

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 limit, profile, campaign_ids and ad_account_id are already fully documented in the schema, including the 'omit to use first ad account' behavior. The description adds no parameter-level syntax or defaults beyond this, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (individual ads / creatives) in a LinkedIn ad account, and enumerates the fields it surfaces (copy, headline, format, status, campaign, Thought Leadership flag). This clearly distinguishes it from performance-oriented siblings like get_ad_performance_breakdown and 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 Guidelines4/5

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

Explicitly routes the agent: pair with get_ad_performance_breakdown to see performance per ad. Implied workflow also references list_ad_accounts and list_ad_campaigns via the schema. It lacks an explicit 'when not to use' or exclusion statement, so it falls short of 5.

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