Skip to main content
Glama

ADS Beast

prepare_google_app_videos_add

Prepare adding videos to a Google App campaign. 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>",
      "campaign_id": "<campaign_id>",
      "reason": "<reason>"
    },
    "name": "prepare_google_app_videos_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShort title.
reasonYesWhy, with numbers (shown to the approver).
client_idYes
account_idNoGoogle account id; needed only when the client has several.
video_urlsNohttps links to mp4 files.
campaign_idYesGoogle Ads id of the App campaign (digits).
youtube_videosNoIds or links of videos already on YouTube.

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=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral facts: nothing is changed in the account, a preview_id is stored with a 15-minute TTL and single use, and execution happens elsewhere. It does not explain validation failures or what the preview contains, but the core contract is disclosed.

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?

Two short sentences with the no-op guarantee and the TTL front-loaded, followed by the next-step pointer. The phrase 'to show' is slightly ambiguous about who sees the preview, but there is essentially no wasted text.

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 7-parameter prepare tool with no output schema, the description covers the safety model, the artifact produced (preview_id), its lifetime, and the execution path. Remaining gaps — whether video URLs are validated, what a preview displays, and behavior when both video sources are supplied — are minor for a staging tool.

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 86%, so the schema already documents nearly every parameter including video_urls, youtube_videos, account_id and reason. The description adds no parameter-level detail — not even that both video_urls and youtube_videos are accepted inputs — so the baseline of 3 applies.

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 ('Prepare adding videos to a Google App campaign') and immediately clarifies the mechanic — it stores a preview_id rather than performing the change. That distinguishes it from execute_prepared_change. The phrasing 'Prepare adding videos' is slightly elliptical, but an agent can still tell what it does without opening the schema.

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?

It explicitly names the follow-up step ('then execute_prepared_change'), so the agent knows this is stage one of a two-step flow. It does not state when to prefer this over other prepare_* siblings or when not to use it, so the guidance is clear but not exhaustive.

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.