Skip to main content
Glama
Sign In
Marvento Ads MCP

Marvento Ads MCP

Official
by MarventoCapital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ads Set Ad Status

ads_set_ad_status
Destructive

Change an ad's status to enabled, paused, or removed. Confirm required for removal to apply changes in Google Ads.

Instructions

Enables, pauses or removes an ad. REMOVED needs confirm=true.

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": {
      "customer_id": "<customer_id>",
      "ad_group_id": "<ad_group_id>",
      "ad_id": "<ad_id>",
      "status": "<status>"
    },
    "name": "ads_set_ad_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesThe ad id.
statusYesENABLED, PAUSED or REMOVED.
confirmNoRequired true for REMOVED.
ad_group_idYesThe ad group the ad belongs to.
customer_idYesGoogle Ads customer id.
validate_onlyNoDry-run only.
login_customer_idNoManager account id if applicable.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already signal readOnly=false and destructive=true. The description adds a meaningful operational constraint by warning that REMOVED requires confirm=true, which is a behavioral gotcha beyond the annotation metadata. It does not contradict 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 two short sentences with the core action front-loaded and the important exception stated immediately after. Every word earns its place, and there is no filler or redundant elaboration.

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?

Given that annotations cover destructive/read-only semantics, the schema documents all 7 parameters including validate_only, and an output schema exists, the description provides the key operational gotcha. It is slightly thin on when to prefer this over sibling status tools, but otherwise sufficient for correct invocation.

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 100%, so the baseline is 3. The only parameter-related detail in the description, 'REMOVED needs confirm=true,' largely restates what the schema already says for the confirm field, adding no new semantic meaning.

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?

The description states a specific verb and resource: 'Enables, pauses or removes an ad.' It clearly names the exact state transitions the tool performs. However, it does not explicitly differentiate this from sibling status tools like ad_groups_set_ad_group_status, so it stops short of full sibling distinction.

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?

The action itself implies when to use the tool: any time an ad's status must be changed. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives, so the agent must infer routing from the tool name and context signals.

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

Deploy Server

Other Tools