Skip to main content
Glama

ADS Beast

google_ads_script_generate

Read-only

Returns a ready Google Ads Script (JavaScript) for one campaign that a person pastes into Google Ads themselves. The tool only produces text. Amounts are in the ad account's own currency, in whole units (not cents or micros).

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": {
      "campaign_id": "<campaign_id>",
      "action": "<action>"
    },
    "name": "google_ads_script_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat the script does.
new_valueNoNew value for the update actions: monthly budget, target CPA or target ROAS.
campaign_idYesADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'the tool only produces text', explaining why nothing is applied on the account. It also adds a genuinely useful behavioral constraint not found in annotations or schema: amounts must be in the account's own currency as whole units, not cents or micros. It does not cover error behavior for invalid campaign ids, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core output and the paste-it-yourself constraint, then the safety clarification, then the units caveat. No filler and nothing redundant with structured fields.

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?

For a 3-parameter, non-mutating generator with no output schema, the description covers the essentials: what is produced, that it is text only, and the unit convention for values. It leaves minor gaps around which actions require new_value and whether the generated script is safe to re-run.

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 100%, so the baseline is 3, but the description goes beyond the schema by specifying the unit convention for new_value (whole currency units, account currency) — a detail the schema omits and one that would otherwise cause a 100x error. It does not clarify what new_value should be omitted for pause/enable actions.

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 gives a specific verb and resource: it returns a ready-to-paste Google Ads Script (JavaScript) for one campaign, and it states the tool only produces text. That clearly separates it from generic generation siblings, though it never names an alternative tool, so an agent must infer the boundary itself.

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?

Usage is implied rather than stated: 'a person pastes into Google Ads themselves' and 'the tool only produces text' signal this is a manual, non-executing path. There is no explicit when-to-use versus when-not, and no mention of the prepare_* siblings that presumably apply changes directly.

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.