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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_reporting_list

Read-onlyIdempotent

Retrieve a reporting list of Google campaigns, ad groups, ads, or keywords by location and date range to review performance data for a chosen integration type.

Instructions

Get reporting list Retrieve a list of Google campaigns or ad groups with reporting data. Deprecated: use GET /ad-publishing/google/reporting/rows with header version: v4. Endpoint: GET /ad-publishing/google/reporting/list (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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>",
      "listType": "<listType>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "type": "<type>"
    },
    "name": "ghl_ad_google_reporting_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesIntegration type
endDateYesReport end date
listTypeYesReport list type
startDateYesReport start date
campaignIdNoCampaign identifier (required when listType is adGroups, ads, or keywords)
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / listType / enum
      Added value: +[
      +  "campaigns",
      +  "ads",
      +  "adGroups",
      +  "keywords"
      +]
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-redundant context: the required OAuth scope (adPublishing.readonly), the underlying endpoint and version header (v3), and deprecation status. It does not describe pagination or result volume, which matters for a reporting list.

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 functional sentence and the deprecation notice before the endpoint/scope metadata, which is the right ordering. The leading 'Get reporting list' line is redundant with the title, but the rest of the text is dense and earns its space.

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?

Covers what it fetches and its deprecation, but with no output schema the description should say something about the shape of the reporting data returned. It also under-describes the listType space relative to the schema's four values, leaving the agent to infer scope from the schema alone.

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% and the schema documents every parameter including the campaignId conditional, so the baseline is 3. The description only loosely echoes listType ('campaigns or ad groups') and says nothing about the date range, locationId, or type enum, adding no meaning beyond the schema.

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 a list of Google campaigns or ad groups with reporting data,' which is far more useful than the tautological title 'Get reporting list.' It does not explicitly distinguish itself from close siblings such as ghl_ad_google_reporting_get or ghl_ad_google_campaign_reporting_get, and it omits two of the listType values (ads, keywords) present in the schema.

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 deprecation warning and points to a specific replacement path (GET /ad-publishing/google/reporting/rows, version header v4), which is a real when-not-to-use signal. It stops short of naming which sibling tool to use instead or when to prefer this over ghl_ad_google_reporting_get, so the routing is only partially complete.

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