Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Upload video asset

ads_upload_video_asset

YouTube-Video als Video-Asset registrieren (URL oder 11-stellige ID) — danach via ads_add_asset_group_assets mit field_type YOUTUBE_VIDEO nutzbar. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "youtube_url": "<youtube_url>"
    },
    "name": "ads_upload_video_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
workspaceNo
youtube_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 mutation profile is covered. The description adds genuine context by clarifying this registers an existing external YouTube video rather than uploading bytes, and it names the follow-up tool needed to actually use the asset. It says nothing about idempotency or what happens if the same video is registered twice, which matters for a create-style call.

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 compact sentences: the action and its input formats come first, then the downstream dependency, then the workspace clarification. No filler. Slightly dense with the German parenthetical, but every clause carries information.

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?

An output schema exists, so return values need not be explained. The description covers purpose, accepted input formats, follow-up usage, and the workspace optionality rule. The remaining gap is the undocumented 'name' parameter and duplicate-handling behavior, which is minor but real for a create 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 coverage is 0%, so the description must carry the load. It does well for two params: youtube_url accepts a URL or an 11-character ID (format detail absent from the schema), and workspace is a customer-workspace slug that is optional when only one workspace exists. The 'name' parameter is never mentioned in either the schema or the description, leaving one of three params 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: register a YouTube video as a video asset, accepting either a URL or an 11-character ID. That is a clear, distinguishable action from the sibling ads_upload_image_asset. It stops short of explicitly differentiating against the other upload/asset tools, so it lands at 4 rather than 5.

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?

Gives a concrete downstream condition: the asset becomes usable via ads_add_asset_group_assets with field_type YOUTUBE_VIDEO. It also states that workspace is optional when only one workspace exists. There is no explicit when-not guidance (e.g. image vs video, or duplicate registration), which keeps it below a 5.

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.

Resources