Skip to main content
Glama

ADS Beast

google_ads_app_videos_check

Read-only

Reads a Google App campaign and validates the videos proposed for it. Read-only.

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>"
    },
    "name": "google_ads_app_videos_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShort title.
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

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so 'Read-only' adds nothing new. What matters for an App campaign video check -- the validation criteria, whether an external YouTube/Ads API lookup occurs, and what the pass/fail result looks like -- is left entirely undisclosed, which is a real gap since no output schema exists.

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 action front-loaded and no filler. The trailing 'Read-only' duplicates the annotation rather than earning its place, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a six-parameter validation tool with no output schema, so the description should explain what a check returns and how the proposed video inputs are handled. Instead it stops at a one-clause purpose statement, leaving the agent unable to predict the result or the input semantics of the optional parameters.

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 83%, so the schema already documents client_id, account_id, campaign_id, title, video_urls and youtube_videos. The description adds no meaning beyond that, and notably it does not explain why a read-only check accepts title, video_urls and youtube_videos as inputs or how the two video sources relate.

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: it reads a Google App campaign and validates the videos proposed for it. That distinguishes it reasonably well from the sibling prepare_google_app_videos_add, though it never says explicitly that it is the check counterpart rather than the write path.

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 phrase 'validates the videos proposed for it' implies the tool is used to vet candidate videos before adding them, but the description gives no explicit when-to-use rule and no exclusions. It never says when this should be preferred over prepare_google_app_videos_add or what to do once validation passes.

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.