microsoft-ads-mcp

delete_keyword

Remove specific keywords from an ad group by providing their IDs and the parent ad group ID.

Instructions

Delete one or more keywords by id.

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>",
      "keyword_ids": "<keyword_ids>"
    },
    "name": "delete_keyword"
  }
}

Input Schema

Name	Required	Description	Default
`ad_group_id`	Yes	The parent ad group id.
`keyword_ids`	Yes	The keyword ids to delete.

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

Behavior2/5

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

Annotations already indicate readOnlyHint=false. The description adds no additional behavioral context beyond 'delete', such as irreversibility, permissions needed, or effect on related data.

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?

A single, clear sentence with no unnecessary information. Every word earns its place.

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?

For a simple delete operation with two parameters and an output schema, the description is adequate but lacks mention of batch behavior, error handling, or permission requirements.

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% with both parameters described. The description does not add extra meaning beyond what the schema already 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 (delete), resource (keywords), and method (by id). It effectively distinguishes from siblings like add_keywords and update_keyword.

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., delete_campaign). No context about prerequisites or exclusions is given.

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

Deploy Server