Marvento Ads MCP

Official

Overview Schema Source Related Servers Discussions Admin

Ads Create Responsive Search Ad

ads_create_responsive_search_ad

Create responsive search ads in an ad group with headlines and descriptions validated against Google's character and policy limits before submission.

Instructions

Creates a responsive search ad in an ad group.

Copy is checked locally against Google's limits before the API call: 3-15 headlines of max 30 chars, 2-4 descriptions of max 90 chars, display paths of max 15 chars, no duplicate lines, no all-caps, no '!' in headlines. Aim for 8-15 distinct headlines and 4 descriptions; Google rates ad strength on variety.

The ad defaults to ENABLED because the campaign is PAUSED until confirmed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path1`	No	Optional display path segment (max 15 chars), e.g. "services".
`path2`	No	Optional second display path segment (requires path1).
`status`	No	ENABLED or PAUSED.	ENABLED
`headlines`	Yes	Plain strings, or objects {text, pin} to pin a headline to position 1-3.
`final_urls`	Yes	Landing page URL(s), https.
`ad_group_id`	Yes	The ad group id.
`customer_id`	Yes	Google Ads customer id.
`descriptions`	Yes	Plain strings, or objects {text, pin} to pin to DESCRIPTION_1/2.
`validate_only`	No	Dry-run. Also runs Google's policy checks without saving.
`login_customer_id`	No	Manager account id if applicable.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.4Sep 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations, the description reveals that copy is validated locally against Google's limits before the API callpa and explains the ENABLED default as intentional because the campaign is PAUSED. This adds meaningful behavioral context without contradicting the annotations.

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 compact and front-loaded: purpose first, then validation details, then a brief strategic recommendation. Every sentence earns its place; the line breaks make the constraints easy to scan.

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

Completeness5/5

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

With a complete input schema, an output schema, and annotations, the description covers the remaining behavioral essentials: local validation, default status rationale, and content best practices. Nothing critical is missing for correct invocation.

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?

Input schema coverage is 100%, but the description adds value by spelling out validation criteria such as headline and description count ranges, character limits, display path constraints, and uniqueness rules. These constraints are not all present in the schema descriptions, so the description compensates usefully.

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 opening sentence uses a specific verb and resource: 'Creates a responsive search ad in an ad group.' This clearly distinguishes the tool from its siblings, especially ads_update_responsive_search_ad, by establishing creation as the operation.

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 concrete guidance on how to call the tool well: aiming for 8-15 headlines and 4 descriptions to improve ad strength, and noting limits like no all-caps and no '!' in headlines. It does not explicitly name alternatives or exclusions, but the create-vs-update distinction is evident from the name and sibling list.

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