Skip to main content
Glama
shinypebble

openai-ads-mcp

by shinypebble

create_campaign

Create an ad campaign with a single budget type (daily or lifetime) in micros, location targeting via country codes, and immutable CPM bidding.

Instructions

Create a campaign. bidding_type is immutable post-creation (default impressions/CPM).

Set exactly one budget — daily_spend_limit_micros OR lifetime_spend_limit_micros (a campaign carries a single budget mode; one is required). Limits are in micros (1_000_000 = one currency unit). country_codes are ISO codes for location targeting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
statusNopaused
daily_spend_limit_microsNo
lifetime_spend_limit_microsNo
bidding_typeNo
country_codesNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
descriptionNo
statusNo
bidding_typeNo
start_timeNo
end_timeNo
budgetNo
targetingNo
serving_issuesNo
created_atNo
updated_atNo
Behavior5/5

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

The description adds important behavioral details beyond annotations: bidding_type is immutable after creation, exactly one budget is required, micros convention, and ISO country codes. Annotations only say not read-only and not destructive, which creation is not.

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 description is concise with two sentences that front-load the main action and then list key constraints. Every part is necessary and no wasted words.

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?

The tool has 7 parameters and an output schema. The description covers the most critical behavioral and formatting nuances (immutability, budget requirement, micros, ISO). It does not mention return values, but the presence of an output schema mitigates that need. Slightly incomplete on status and description, but overall adequate.

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?

Given 0% schema description coverage, the description compensates well by explaining semantics for bidding_type (immutable, default), budget limits (mutually exclusive, micros), and country_codes (ISO). However, status and description parameters are not explained, leaving some gaps.

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 clearly states 'Create a campaign' with specific verb and resource. It distinguishes this tool from siblings like update_campaign, get_campaign, etc., by focusing on creation and providing key constraints.

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 description gives clear usage context: when to create a campaign, with rules about budget and bidding_type. It does not explicitly state when not to use it (e.g., use update_campaign for modifications), but the intent is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinypebble/openai-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server