Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_asset_list

Read-onlyIdempotent

Retrieve Google Ads creative assets for a location and page through results using limit and pageToken; returns a plain array or a paginated assets envelope.

Instructions

Get assets Retrieve Google Ads creative assets for a location. Without limit the response is a plain array of assets. When limit is provided (max 100, default 100) the response is a paginated { assets, paging } envelope; pass pageToken (from paging.next) to fetch the next batch. Endpoint: GET /ad-publishing/google/assets (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly Pagination params: limit — pass them to page through full result sets.

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": {
      "locationId": "<locationId>",
      "type": "<type>"
    },
    "name": "ghl_ad_google_asset_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAsset identifier
typeYesAsset type to retrieve
limitNoPage size for a paginated fetch (max 100, defaults to 100). When set, the response is a { assets, paging } envelope instead of a plain array.
pageTokenNoOpaque cursor for the next batch, taken from the previous response paging.next
locationIdYesLocation identifier
advertiserOnlyNoAdvertiser only flag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / id / example
      Previous value: -"asset_123"New value: +"123456789"
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size for a paginated fetch (max 100, defaults to 100). When set, the response is a { assets, paging } envelope instead of a plain array.",
      +  "example": "100",
      +  "type": "string"
      +}
    • addedInput schema / properties / pageToken
      Added value: +{
      +  "description": "Opaque cursor for the next batch, taken from the previous response paging.next",
      +  "example": "100",
      +  "type": "string"
      +}
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "CALL",
      -  "SITELINK",
      -  "LEAD_FORM",
      -  "IMAGE",
      -  "TEXT"
      -]New value: +[
      +  "CALL",
      +  "SITELINK"
      +]
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered; the description adds the conditional response shape, the endpoint and version header, and the required `adPublishing.readonly` OAuth scope. What's missing is anything about rate limits or truncation behavior beyond the 100 cap.

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?

Front-loaded with the core action and the response-shape distinction, then supporting metadata. The final sentence about pagination params is garbled and adds no information, costing a point.

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?

No output schema exists, and the description compensates by explaining both return shapes (array vs `{ assets, paging }` envelope) and how to continue paging. Required parameters and auth scope are covered; only the roles of `id` and `advertiserOnly` are left entirely to the schema.

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 100%, so the schema already documents `limit` (max 100, default 100, envelope trigger), `pageToken` (from `paging.next`), `type` enum, and `locationId`. The description largely restates these rather than adding new meaning; the trailing line "Pagination params: limit — pass them" is redundant and even omits `pageToken`. Baseline 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?

States a specific verb and resource: "Retrieve Google Ads creative assets for a location," which clearly separates it from the mutating sibling ghl_ad_google_asset_upsert. It doesn't explicitly name or contrast with any sibling, which keeps it below a 5.

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?

Gives useful conditional guidance on the two response modes (no `limit` = plain array, `limit` set = paginated envelope with `pageToken` from `paging.next`). However, it never says when to reach for this tool versus the upsert/other asset tools, so the selection guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools