Skip to main content
Glama

Google ads library

google_ads_library
Read-onlyIdempotent

Reads a Google Ads account's pictures (assetId, address and size, the newest that fit with the account's count, or those whose name holds the words of search), its YouTube videos, its audience lists and its audiences. Pictures and videos are reused by id in google_ads_build; audience lists are what an ad group's audienceLists name, and audiences name a signal for a Performance Max asset group. google_ads_build accepts only pictures listed here or given by the person.

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": {
      "input": "<input>"
    },
    "name": "google_ads_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / input / properties / search
      Added value: +{
      +  "description": "A word of a picture's name",
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still contributes real behavior: the picture list is capped to "the newest that fit with the account's count," and search matches words within a picture's name rather than exact names. It does not mention per-resource result shapes or limits for videos/audiences, which keeps it below 5.

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

Conciseness3/5

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

The purpose is front-loaded and there is no filler, but the first sentence is a long run-on with a dense parenthetical wedged mid-clause, forcing the reader to parse four resource types at once. The relationship sentence is valuable but could be split for readability.

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?

With no output schema, the description carries the burden of describing returns; it lists fields only for pictures (assetId, address, size) and leaves the video and audience result shapes unexplained. For a tool covering four resource families, that is adequate but leaves the agent guessing what it will actually receive.

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 75%, so the baseline is 3; userStatement, accountIds and idempotencyKey are already documented in the schema. The description adds a little meaning to `search` (word-matching against picture names) beyond the schema's terse "A word of a picture's name," but says nothing about accountId scoping or the accountIds narrowing parameter.

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 opens with a specific verb ("Reads") and enumerates the exact resources: pictures with assetId/address/size, YouTube videos, audience lists and audiences. It also names the consuming sibling (google_ads_build), so an agent can tell this is the asset-inventory reader rather than a builder. It stops short of 5 because bundling four distinct resource types into one tool leaves the boundary of a single call slightly fuzzy.

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?

Usage is implied rather than stated: pictures and videos are "reused by id in google_ads_build" and build "accepts only pictures listed here," which tells the agent to call this before building creative. There is no explicit when-to-use/when-not framing and no comparison against other asset-related siblings such as campaign_media or creative_market_evidence.

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.