Skip to main content
Glama

Nuntior

by com.nuntior.mcp
OverviewDiscussionsAdmin

Paid Social Ad Campaigns & Post Boosting

ads_campaigns
Idempotent

Create, list, pause, resume, inspect metrics, or boost organic posts into paid social ad campaigns across LinkedIn Ads, X Ads, Meta (Facebook/Instagram) Ads, and TikTok Spark Ads with 0% Nuntior ad-spend commission. Use this tool when an organic post performs strongly and should be amplified to a targeted B2B or consumer audience with a controlled daily budget. Returns campaign configuration, status, targeting parameters, and real-time spend/conversion snapshots.

Input Schema

NameRequiredDescriptionDefault
nameNoHuman-readable campaign name (e.g. 'Q4 AI Agent Launch — LinkedIn Sponsored Update').
actionYesPaid ads operation: 'list' campaigns, 'create' a new campaign, 'boost_post' to turn an existing organic post into a paid ad, 'pause' or 'resume' delivery, or fetch 'metrics'.
platformNoTarget ad network platform (e.g. 'linkedin', 'x', 'facebook', 'instagram', 'tiktok').linkedin
objectiveNoCampaign optimization objective: 'leads' (lead gen forms/signups), 'traffic' (website clicks), 'engagement' (likes/replies), or 'awareness' (reach/impressions).leads
profileIdNoBrand profile identifier (`prof_...`) linked to the ad account.prof_allometrik
targetingNoStructured audience targeting criteria such as countries, job titles, industries, or interest keywords (e.g. `{ "countries": ["US", "AE", "ES"], "titles": ["CTO", "Founder"] }`).
campaignIdNoAd campaign identifier (`camp_...`). Required when pausing, resuming, or querying a specific campaign.
postIdToBoostNoExisting Nuntior organic post ID (`post_...`) to promote when `action` is 'boost_post'.
dailyBudgetUsdNoDaily ad spend cap in USD (e.g. 25 for $25/day). Nuntior charges 0% markup on ad spend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / description
      Added value: +"Paid ads operation: 'list' campaigns, 'create' a new campaign, 'boost_post' to turn an existing organic post into a paid ad, 'pause' or 'resume' delivery, or fetch 'metrics'."
    • addedInput schema / properties / campaignId / description
      Added value: +"Ad campaign identifier (`camp_...`). Required when pausing, resuming, or querying a specific campaign."
    • addedInput schema / properties / dailyBudgetUsd / default
      Added value: +25
    • addedInput schema / properties / dailyBudgetUsd / description
      Added value: +"Daily ad spend cap in USD (e.g. 25 for $25/day). Nuntior charges 0% markup on ad spend."
    • addedInput schema / properties / name / description
      Added value: +"Human-readable campaign name (e.g. 'Q4 AI Agent Launch — LinkedIn Sponsored Update')."
    • addedInput schema / properties / objective / default
      Added value: +"leads"
    • addedInput schema / properties / objective / description
      Added value: +"Campaign optimization objective: 'leads' (lead gen forms/signups), 'traffic' (website clicks), 'engagement' (likes/replies), or 'awareness' (reach/impressions)."
    • addedInput schema / properties / platform / default
      Added value: +"linkedin"
    • addedInput schema / properties / platform / description
      Added value: +"Target ad network platform (e.g. 'linkedin', 'x', 'facebook', 'instagram', 'tiktok')."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "x",
-  "linkedin",
-  "instagram",
-  "facebook",
-  "threads",
-  "tiktok",
-  "youtube",
-  "bluesky",
-  "mastodon",
-  "farcaster",
-  "reddit",
-  "pinterest",
-  "google_business",
-  "telegram",
-  "discord",
-  "ghost",
-  "wordpress",
-  "webflow"
-]New value: +[
+  "x",
+  "linkedin",
+  "bluesky",
+  "instagram",
+  "facebook",
+  "threads",
+  "tiktok",
+  "youtube",
+  "reddit",
+  "pinterest",
+  "mastodon",
+  "telegram",
+  "discord",
+  "google_business",
+  "ghost",
+  "wordpress",
+  "webflow",
+  "whatsapp"
+]
    • addedInput schema / properties / postIdToBoost / description
      Added value: +"Existing Nuntior organic post ID (`post_...`) to promote when `action` is 'boost_post'."
    • addedInput schema / properties / profileId / default
      Added value: +"prof_allometrik"
    • addedInput schema / properties / profileId / description
      Added value: +"Brand profile identifier (`prof_...`) linked to the ad account."
    • addedInput schema / properties / targeting / description
      Added value: +"Structured audience targeting criteria such as countries, job titles, industries, or interest keywords (e.g. `{ \"countries\": [\"US\", \"AE\", \"ES\"], \"titles\": [\"CTO\", \"Founder\"] }`)."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

It discloses key behavioral traits beyond the schema and annotations, such as the business advantage of '0% Nuntior ad-spend commission' and the exact data returned ('real-time spend/conversion snapshots').

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?

The text is dense but efficient, using every sentence to convey either a capability, a scope, a business benefit, or an output specification. It is perfectly sized for its complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's multi-platform nature and the breadth of its functions, the description is highly complete, covering the full lifecycle of an ad campaign and the context of its operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema is complete, the description reinforces the scope by listing specific supported platforms and clearly linking the 'boost_post' action to the strategic use case, helping the agent choose the correct parameters.

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?

The description provides an exhaustive list of capabilities: 'Create, list, pause, resume, inspect metrics, or boost organic posts.' This clearly defines the scope of the tool beyond just 'ads_campaign' and specifies the platforms it supports.

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

Usage Guidelines5/5

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

It provides a perfect 'when-to-use' scenario: 'Use this tool when an organic post performs strongly and should be amplified.' This is highly effective for routing the agent when a post goes viral organically.

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

All Nuntior toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources