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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_reporting_get

Read-onlyIdempotent

Retrieve aggregated Google Ads metrics for a location by specifying fields, date range, and integration type to analyze campaign performance.

Instructions

Get reporting data Retrieve aggregated Google Ads reporting metrics for a location Endpoint: GET /ad-publishing/google/reporting (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>",
      "fields": "<fields>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "type": "<type>"
    },
    "name": "ghl_ad_google_reporting_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesIntegration type
fieldsYesReporting fields. Pass as comma-separated values on the wire (e.g. ?fields=impressions,clicks).
endDateYesReport end date
groupByNoGroup by period
startDateYesReport start date
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / type / example
      Previous value: -"AD_MANAGER or INTEGRATION"New value: +"INTEGRATION"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by naming the required OAuth scope (adPublishing.readonly), the version header (v3), and the underlying endpoint, which an agent needs to reason about access failures.

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 and compact, with the core action first and endpoint/scope metadata after. 'Get reporting data' restates the title redundantly, a minor waste, but nothing else is padding.

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?

A read-only, fully-schema-covered query is adequately described, and annotations carry the safety profile. But there is no output schema and the description only says 'aggregated metrics' without indicating response shape, so combined with the undifferentiated siblings it is minimum-viable rather than complete.

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 every parameter (type, fields, dates, groupBy, locationId) is already documented in the schema. The description adds no parameter-level meaning, so the 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+resource ('Get reporting data', 'Retrieve aggregated Google Ads reporting metrics for a location'), which is clear. However, it never differentiates from close siblings like ghl_ad_google_reporting_list or ghl_ad_google_campaign_reporting_get, so the agent must infer which reporting tool applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing says when to use this versus the list or campaign-level reporting siblings, and no prerequisites or exclusions are given. The endpoint/scope lines are operational context, not usage guidance.

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