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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_campaign_reporting_get

Read-onlyIdempotent

Retrieve reporting metrics for a specific Google Ads campaign using campaign ID, location ID, and date range to analyze performance.

Instructions

Get campaign reporting Retrieve reporting metrics for a specific Google campaign Endpoint: GET /ad-publishing/google/reporting/campaign/{campaignId} (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": {
      "campaignId": "<campaignId>",
      "locationId": "<locationId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ghl_ad_google_campaign_reporting_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesReport end date
startDateYesReport start date
campaignIdYesCampaign identifier
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / campaignId / example
      Previous value: -"camp_abc123"New value: +"507f1f77bcf86cd799439011"
  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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely useful behavior beyond that: the required OAuth scope adPublishing.readonly and the API version header, which tell the agent about auth prerequisites. It does not describe the metrics returned or any rate limits.

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?

Short, front-loaded, and free of padding, though the first two lines ('Get campaign reporting' and 'Retrieve reporting metrics...') largely duplicate each other. Technical metadata is grouped cleanly at the end.

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 definition should say something about what reporting metrics come back or their shape; it only says 'reporting metrics'. Auth scope and endpoint are covered, but the agent gets no idea of the response payload for a data-retrieval tool.

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% with four documented parameters including examples, so the schema carries parameter meaning. The description adds no format or semantics beyond that, which is acceptable at this coverage level but nothing more.

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 reporting metrics for a specific Google campaign, reinforced by the exact endpoint path. It does not distinguish itself from close siblings such as ghl_ad_google_reporting_get or ghl_ad_google_reporting_list, so an agent must infer the difference.

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?

There is no statement of when to use this tool versus the generic ghl_ad_google_reporting_get or the list variant. The endpoint and scope lines give technical context but no selection guidance or exclusions.

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