Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Dismiss recommendation

ads_dismiss_recommendation
Destructive

Eine Google-Ads-Empfehlung verwerfen (resource_name aus ads_list_recommendations). workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "resource_name": "<resource_name>"
    },
    "name": "ads_dismiss_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
resource_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is carried by structured data. The description adds the workspace-optionality rule but says nothing about irreversibility, whether a dismissed recommendation can be restored, or permission requirements — modest value on top of 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?

Two short lines, zero filler, with the core action first and the parameter notes second. Nothing could be removed without losing information.

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?

Only two parameters and an output schema exists, so return values need no explanation; both params are covered in the text. For a destructive mutation the description could still say more about consequences, but annotations cover the safety signal.

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?

Schema coverage is 0%, so the description must carry both parameters, and it does: resource_name is sourced from ads_list_recommendations, and workspace is described as optional when only one workspace exists. It lacks any format/identifier detail for resource_name beyond the source tool.

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 ('verwerfen'/dismiss) plus a specific resource ('Google-Ads-Empfehlung'), so an agent knows exactly what the tool does. It doesn't explicitly contrast with the natural sibling ads_apply_recommendation (accept instead of dismiss), which keeps it short of a 5.

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?

Points the agent to ads_list_recommendations as the source of resource_name, which is real workflow guidance rather than none. It never states when to dismiss vs. apply a recommendation or any prerequisite, so the exclusion side is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources