SelieeAI

Create Ads Campaign From Audience

create_ads_campaign_from_audience

Destructive

[write] Create a campaign that targets an audience (ads_audience_id or ads_audience_uuid; must be targetable) - same as create_ads_campaign without the ad account, which comes from the audience - and publish it PAUSED (it cannot spend until activate_ads_campaign). ads_audience_exclude_ids lists audiences of the same account to exclude (Meta, LinkedIn). Website defaults to the audience's, then the account's.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ads_campaign_title": "<ads_campaign_title>",
      "ads_campaign_goal": "<ads_campaign_goal>",
      "ads_campaign_daily_budget": "<ads_campaign_daily_budget>"
    },
    "name": "create_ads_campaign_from_audience"
  }
}

Input Schema

Name	Required	Description	Default
`ads_audience_id`	No
`ads_audience_uuid`	No
`ads_campaign_goal`	Yes
`seliee_website_id`	No
`ads_campaign_title`	Yes
`seliee_website_uuid`	No
`ads_campaign_creative`	No
`ads_campaign_end_date`	No
`ads_campaign_targeting`	No
`ads_campaign_custom_url`	No
`ads_campaign_start_date`	No
`ads_audience_exclude_ids`	No
`ads_campaign_daily_budget`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare write/openWorld/non-idempotent/destructive, but the description adds behavior they cannot convey: the campaign is created paused and "cannot spend until activate_ads_campaign," so an agent understands the object is inert after creation. It also discloses that exclusions apply only within the same account and only on Meta/LinkedIn, a platform-specific caveat.

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 dense paragraph with a leading [write] tag and the key constraint (paused, no spend) front-loaded before the parameter notes. The nested parentheticals make it slightly hard to parse, but every clause carries actionable information.

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 13-parameter mutation with no output schema, the description covers the creation semantics, the audience prerequisite, the paused state, and the platform-specific exclusion rule. It does not say what the call returns (e.g., campaign identifier) or how non-targetable audiences fail, which an agent would want for error handling, but the core calling information is present.

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?

With 0% schema description coverage across 13 parameters, the description carries the burden and does explain the least obvious ones: ads_audience_id/ads_audience_uuid are an either/or selector requiring a targetable audience, ads_audience_exclude_ids is a same-account list, and the website resolves from audience then account. It leaves the numerous campaign fields (goal, creative, targeting, custom_url, dates, budget) unaddressed, though their names are largely self-describing.

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 and resource ("Create a campaign that targets an audience") and explicitly positions it against the sibling create_ads_campaign ("same as create_ads_campaign without the ad account, which comes from the audience"). The added detail that it publishes PAUSED further distinguishes its effect from a plain create.

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?

Names the alternative (create_ads_campaign) and the exact condition that selects this tool instead: the ad account is derived from the audience rather than passed in. It also states the prerequisite ("must be targetable") and the required follow-up tool (activate_ads_campaign) before any spend can occur.

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

All SelieeAI tools Inspect

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.