Caybl

Create a Search campaign

create_campaign

Create a Search campaign against an existing budget. Created PAUSED by default so it cannot start spending before a human looks at it - pass status='ENABLED' only when that is intended. Create the budget first with create_campaign_budget.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Campaign name, unique within the account.
`status`	No	Defaults to PAUSED. A campaign created ENABLED can begin serving and spending immediately.	PAUSED
`endDate`	No	YYYYMMDD. Omit to run indefinitely.
`budgetId`	Yes	Campaign budget id from create_campaign_budget.
`startDate`	No	YYYYMMDD. Defaults to today.
`customerId`	No	10-digit Google Ads customer id. Omit only if this connection has exactly one reachable account - with more than one, omitting it errors and lists the available ids to pick from.
`extraFields`	No	Escape hatch for a field Google requires that this tool doesn't set yet - use it when a prior call to this same tool failed naming a required field and its valid values (e.g. after adding `contains_eu_political_advertising`, retry with { contains_eu_political_advertising: "DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING" }). Keys are the Ads API's own snake_case field names; nest an object to add a field under one this tool already sets (e.g. a new network_settings sub-field). Only ADDS fields not already set by this tool's own arguments - it can never override `status` or any other field already set here, so it cannot be used to bypass validation or a safety default like a campaign's PAUSED-by-default status.
`validateOnly`	No	Dry run. When true the Google Ads API validates the change and reports any errors but applies nothing. Use this first whenever you are unsure - it is free and cannot affect spend.
`searchNetwork`	No	Also serve on Google search partners.
`contentNetwork`	No	Also serve on the Display network.
`biddingStrategy`	No	MAXIMIZE_CONVERSIONS needs conversion tracking already working, or delivery will suffer.	MANUAL_CPC

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the generic profile (not read-only, open-world, non-idempotent). The description adds what they cannot: the campaign is created PAUSED as a safety default so it cannot spend before human review, and the extraFields escape hatch can never override status or other safety defaults. That is exactly the mutation-safety context an agent needs before spending money.

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?

Three short sentences, front-loaded with the action, then the safety default, then the prerequisite. No filler, and the riskiest piece of information (ENABLED is opt-in) is stated early.

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 an 11-parameter mutation tool with no output schema, the description covers purpose, prerequisite, and safety defaults well. It does not say what a successful call returns (e.g. the new campaign id), which an agent chaining into update_campaign would want, but the schema and annotations otherwise carry the load.

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 baselines to 3, and the schema already explains status defaults, extraFields, validateOnly, and customerId resolution in depth. The description restates the status default rather than adding syntax or new parameter meaning, so it does not exceed the schema baseline.

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 Search campaign') plus a key constraint ('against an existing budget'), which implicitly separates it from budget-creation siblings. It explicitly names create_campaign_budget, so an agent can route correctly without opening either schema.

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?

Gives an explicit prerequisite ('Create the budget first with create_campaign_budget') and an explicit when-to-use condition for the risky path ('pass status=ENABLED only when that is intended'). The default-PAUSED guidance tells the agent which behavior to expect when it says nothing.

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

All Caybl 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.

Resources

Need Help?