Caybl

Create a responsive search ad

create_responsive_search_ad

Create a responsive search ad in an ad group. Google requires 3 to 15 headlines (max 30 chars each) and 2 to 4 descriptions (max 90 chars each); those limits are enforced here before the call so a bad draft fails fast rather than as an opaque API error. Created PAUSED by default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path1`	No	First display-URL path segment.
`path2`	No	Second display-URL path segment.
`status`	No		PAUSED
`finalUrl`	Yes	Landing page URL, including https://.
`adGroupId`	Yes
`headlines`	Yes	3-15 headlines, max 30 characters each.
`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.
`descriptions`	Yes	2-4 descriptions, max 90 characters each.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (openWorldHint, non-idempotent, non-destructive), the description discloses genuinely useful behavior: Google's headline/description limits are enforced before the API call for fail-fast validation, and the ad is created PAUSED by default. That 'enforced here so a bad draft fails fast rather than as an opaque API error' detail is real added context.

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?

Three front-loaded sentences: purpose first, then the enforcement/limits rationale, then the safety default. Tight overall, though the limits sentence partially duplicates schema constraints and could be trimmed.

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 10-parameter mutation tool with no output schema, the description covers the essential safety default (PAUSED) and the validation behavior. Parameter-level detail and the customerId/extraFields semantics are left to the schema (80% coverage), which is acceptable, so little is missing.

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 high (80%), so the schema already documents most parameters, including the headline/description counts and character limits and the PAUSED status default. The description restates those limits but adds no syntax or meaning beyond the schema; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 responsive search ad in an ad group' — so the agent knows exactly what the tool does. It distinguishes itself from sibling create_* tools by resource type (responsive search ad vs campaign, ad group, budget), but doesn't explicitly name or contrast any sibling.

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

Usage Guidelines3/5

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

Usage is only implied: the agent infers you use this to build a new RSA rather than calling an update or get tool. There is no explicit when/when-not guidance and no named alternative (though there happens to be no other ad-creation sibling to route to).

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?