Skip to main content
Glama

B2B Creators

by com.b2b-creators.mcp
OverviewDiscussionsAdmin

Per-ad performance breakdown

get_ad_performance_breakdown
Read-onlyIdempotent

Rank individual ads by spend with impressions, clicks, CTR, CPC, engagement, leads, cost per lead and video views, joined with the ad copy. Use to work out which ads are working, and to compare cost per outcome against the organic reach the team's profiles produce for free. Thought Leadership ads are flagged, which is the closest paid equivalent to a personal post.

Input Schema

NameRequiredDescriptionDefault
limitNoMax ads to return. Defaults to 30.
profileNoOptional. An ads connection sessionId from list_profiles → adsConnections. Person names are ignored for ads: the workspace's shared LinkedIn Ads connection is used.
end_dateNoYYYY-MM-DD, defaults to today.
start_dateNoYYYY-MM-DD, defaults to 30 days ago.
campaign_idsNoOptional campaign ids from list_ad_campaigns to scope the analysis.
creative_idsNoOptional specific ad ids from get_ad_creatives.
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
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. Beyond that, the description discloses genuinely useful behavior: results are ranked by spend, ad copy is joined in, and Thought Leadership ads are flagged. It omits row limits, ordering ties, or empty-result behavior, but the added context is solid for a read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is dense and front-loaded with the actual capability. The following two sentences drift into positioning language ('the closest paid equivalent to a personal post', organic reach comparison) that is loosely actionable for routing but not essential.

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?

No output schema exists, yet the description names the returned metrics and the ranking basis, so an agent knows what comes back. With 100% schema coverage on inputs and read-only annotations, the definition is sufficient, though sibling differentiation and pagination behavior remain thin.

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% and the schema documents all seven parameters (limit default 30, date defaults, campaign/creative id sources, ad account fallback). The description adds no parameter-level detail, so the 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 and resource ('Rank individual ads by spend') and enumerates the metrics returned (impressions, clicks, CTR, CPC, engagement, leads, cost per lead, video views) plus the join with ad copy. It does not name its closest sibling get_ads_performance, so the granularity distinction (per-ad vs. account-level) must be inferred.

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?

'Use to work out which ads are working' gives an implied use case but never states when to choose this over get_ads_performance or get_ad_creatives, nor any exclusion or prerequisite. Usage must be inferred from the tool name.

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