Skip to main content
Glama
geopopos

NewsBreak MCP Server

by geopopos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create Ad Set

newsbreak_create_ad_set

Create an ad set inside a NewsBreak campaign by specifying budget, bid type, targeting, schedule, and frequency caps to control delivery.

Instructions

Create a new ad set within a campaign.

Args:

  • campaignId (string, required): ID of the parent campaign

  • name (string, required): Ad set name

  • budgetType (string, required): DAILY or TOTAL

  • budget (number, required): Budget in cents

  • startTime (number, required): Start timestamp (Unix epoch seconds)

  • endTime (number, required): End timestamp (Unix epoch seconds)

  • bidType (string, required): CPM, CPC, TARGET_CPA, TARGET_ROAS, MAX_CONVERSION, etc.

  • bidRate (number, optional): Bid rate in cents (required for CPM, CPC, TARGET_CPA)

  • roas (number, optional): ROAS value (required for TARGET_ROAS types)

  • deliveryRate (string, optional): EVENLY or ASAP

  • trackingId (string, optional): Event tracking ID (required for conversion bid types)

  • targeting (object, optional): Audience targeting with dimensions like location, gender, ageGroup, etc.

  • schedule (object, optional): Day/hour schedule map

  • frequencyCaps (array, optional): Frequency cap settings

  • status (string, optional): ON or OFF. Default: ON

Returns: Created ad set details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDescriptive name of the ad set
roasNoROAS value (required for TARGET_ROAS, DAY_ONE_TARGET_ROAS)
budgetYesBudget in cents
statusNoStatus: ON or OFF. Default is ON
bidRateNoBid rate in cents (required for CPM, CPC, TARGET_CPA)
bidTypeYesBid type: CPM, CPC, TARGET_CPA, TARGET_ROAS, etc.
endTimeYesEnd timestamp (Unix epoch)
iosAppIdNoiOS App Store URL (required for APP_TRAFFIC campaigns)
scheduleNoSchedule map: day of week (0-6) to hours (0-23)
startTimeYesStart timestamp (Unix epoch)
targetingNoAudience targeting criteria
budgetTypeYesBudget type: DAILY or TOTAL
campaignIdYesID of campaign
trackingIdNoEvent tracking ID (required for conversion-based bid types)
deliveryRateNoDelivery rate: EVENLY or ASAP (for CPM, CPC only)
googlePlayIdNoAndroid app package name (required for APP_TRAFFIC campaigns)
frequencyCapsNoFrequency cap settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and idempotentHint=false, so the mutation behavior is not a surprise. The description adds only 'Returns: Created ad set details' and restates some parameter-level requirements, but does not disclose additional behavioral context such as side effects, failure modes, or what happens when required bid fields are missing.

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 purpose statement is front-loaded and clear, but the subsequent 17-line Args block largely duplicates the input schema line-by-line. This is structured and readable, yet not concise for an agent that already has access to the full schema; the duplication adds length without adding value.

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

Completeness3/5

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

For a complex 17-parameter creation tool with no output schema, the description leaves the response only as 'Created ad set details,' which is vague and does not tell the agent what fields to expect. Input semantics are well-covered by the schema, but the lack of output detail and explicit prerequisites beyond campaignId makes it only minimally complete.

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 the input schema already documents every parameter thoroughly. The description's Args section mostly restates the schema's existing information (e.g., 'Budget in cents', 'required for CPM, CPC, TARGET_CPA') without adding meaningful new semantics beyond what the schema provides.

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 opens with 'Create a new ad set within a campaign,' naming a specific action, object, and parent scope. This makes it immediately distinguishable from sibling tools like newsbreak_create_campaign and newsbreak_create_ad, and from the update_ad_set variant.

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?

The phrase 'within a campaign' and the required campaignId parameter clearly establish that this tool is for creating ad sets under an existing campaign, not for retrieving or updating them. It does not explicitly name alternatives or say when not to use it, but the context is sufficient for correct selection among siblings.

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

Deploy Server

Other Tools