Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Add asset group assets

ads_add_asset_group_assets

Bestehende Assets an eine Asset Group hängen. assets: [{"asset_id","field_type"}] mit field_type HEADLINE, LONG_HEADLINE, DESCRIPTION, MARKETING_IMAGE, SQUARE_MARKETING_IMAGE, PORTRAIT_MARKETING_IMAGE, LOGO, BUSINESS_NAME oder YOUTUBE_VIDEO. 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": {
      "asset_group_id": "<asset_group_id>",
      "assets": "<assets>"
    },
    "name": "ads_add_asset_group_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYes
workspaceNo
asset_group_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety profile is covered. The description adds that assets are merely attached (additive, not replacing the group's contents), but says nothing about what happens on duplicate field_type conflicts, partial failures, or whether repeated calls are idempotent — meaningful gaps for a mutation tool.

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 dense sentences, front-loaded with the action and followed by the two non-obvious parameters. The long comma-separated field_type list is slightly unwieldy but every element is load-bearing information.

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

Completeness3/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 described. Still, for a mutation tool with 0% schema coverage the description omits the ordering/precondition story (assets must be uploaded first, asset group must exist, field_type must match the group's campaign type), which is exactly the context an agent needs before calling it.

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 description coverage is 0% and the assets array is typed only as a free-form object, so the description carries the full load — and it does: it documents the {"asset_id", "field_type"} shape and enumerates all nine valid field_type values, which the schema does not. workspace is explained as an optional customer slug; only asset_group_id is left to the agent's obvious reading of the name.

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 German sentence 'Bestehende Assets an eine Asset Group hängen' gives a specific verb (attach) and resource (existing assets → asset group), which is unambiguous. It does not, however, distinguish itself from closely related siblings such as ads_link_asset, ads_create_text_assets, or ads_upload_image_asset, so an agent still has to infer the boundary.

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?

'Bestehende Assets' implies prerequisites (assets must already exist, asset group must exist), but this is left implicit — no explicit when-to-use, when-not, or named alternative is given. With ~80 sibling tools in the ads_* family, this leaves the agent to infer the workflow rather than routing it.

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