microsoft-ads-mcp

create_responsive_search_ad

Creates a paused Responsive Search Ad in Microsoft Advertising with specified headlines, descriptions, and landing page URL for ad groups.

Instructions

Create a Responsive Search Ad (PAUSED).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_group_id": "<ad_group_id>",
      "final_url": "<final_url>",
      "headlines": "<headlines>",
      "descriptions": "<descriptions>"
    },
    "name": "create_responsive_search_ad"
  }
}

Input Schema

Name	Required	Description
`path1`	No	Optional display URL path 1 (max 15 chars).
`path2`	No	Optional display URL path 2 (max 15 chars).
`final_url`	Yes	Landing page URL.
`headlines`	Yes	3-15 headlines (truncated to 30 chars each).
`ad_group_id`	Yes	The ad group id.
`descriptions`	Yes	2-4 descriptions (truncated to 90 chars each).
`final_url_suffix`	No	Optional Final URL suffix appended to landing-page URLs.
`tracking_url_template`	No	Optional tracking template for this ad's URLs.
`url_custom_parameters`	No	Optional {key: value} URL custom parameters, referenced in templates/suffixes as {_key}.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`ids`	No
`message`	Yes
`partial_errors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations indicate readOnlyHint=false, so the description's 'Create' is consistent. The paused state is a helpful behavioral detail. However, no other behavioral traits are disclosed (e.g., auth requirements, rate limits, overwrite behavior). The description adds minimal value beyond annotations.

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 description is extremely concise (one sentence) and front-loaded with key info. However, it is arguably too terse for a complex tool with 9 parameters, lacking contextual detail that would aid understanding without extra scanning.

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?

Given the existence of an output schema and full schema parameter coverage, the description doesn't need to explain return values. However, it fails to provide high-level context such as validation rules, required permissions, or relationship to other tools (e.g., ad groups). It meets the minimum but is not comprehensive.

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 coverage is 100%, so the schema already documents all parameters and their descriptions. The tool description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 the action ('Create'), the resource ('Responsive Search Ad'), and the initial state ('PAUSED'), which distinguishes it from the sibling tool 'update_responsive_search_ad'. The purpose is unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., when to create an active ad instead of paused, or prerequisites like ad group existence). The description lacks any contextual usage tips.

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

Deploy Server