Skip to main content
Glama

ADS Beast

prepare_google_rsa_variations

Prepare additional responsive search ads for a client's Google campaigns. New ads are created paused. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "client_id": "<client_id>",
      "ad_variations": "<ad_variations>",
      "reason": "<reason>"
    },
    "name": "prepare_google_rsa_variations"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
client_idYes
campaign_idsNoADS Beast ids from list_campaigns.
ad_variationsYesAd variations, each naming its campaign and ad group.
verify_ad_strengthNoRead Ad Strength back after upload.
require_full_assetsNoRequire 15 headlines and 4 descriptions per ad.
create_missing_ad_groupsNoAllow creating ad groups that do not exist yet.
min_new_ads_per_campaignNoMinimum number of new ads per campaign.

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?

Adds real behavior beyond the annotations: ads land paused, nothing is committed, the preview_id lives 15 minutes and is single-use, and execution is a separate step. The annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) are broadly consistent, but the mixed message between 'New ads are created paused' and 'Changes nothing' is a minor clarity gap an agent must resolve on its own.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with the core action and the hand-off both front-loaded; nothing is filler. The 'Changes nothing' clause is slightly at odds with the preceding sentence, costing a bit of clarity in an otherwise efficient layout.

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 an 8-parameter staging tool with no output schema, the description covers the essential contract: nothing commits, a single-use preview_id comes back for display, and execution is a separate tool. It leaves permission/prerequisite details and client_id semantics to the schema and annotations, which is acceptable here.

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 88%, so the schema already explains reason, campaign_ids, ad_variations, verify_ad_strength, require_full_assets, create_missing_ad_groups and min_new_ads_per_campaign. The description adds no parameter-level meaning, notably nothing about client_id, which the schema leaves undocumented.

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 and resource: 'Prepare additional responsive search ads' for Google campaigns, and names the follow-up tool execute_prepared_change. However, the phrase 'New ads are created paused' sits uneasily next to the tool's 'prepare' framing, leaving slight doubt about whether ads are actually created by this call or only staged.

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?

The description gives the operational sequence explicitly: call this to stage, store the preview_id, show it, then call execute_prepared_change. It does not state when not to use it (e.g., versus the other prepare_* siblings or when assets are missing), but the workflow context is clear.

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.