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

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_entity_get

Read-onlyIdempotent

Retrieve Google Ads campaigns, ad groups, or ads by entity type and filter results by location, date range, campaign, ad group, or Google Ads IDs.

Instructions

Get entities Retrieve Google campaigns, ad groups, or ads based on entity type Endpoint: GET /ad-publishing/google/entity (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>",
      "type": "<type>",
      "entityType": "<entityType>"
    },
    "name": "ghl_ad_google_entity_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesIntegration type
endDateNoFilter end date
searchIdNoComma-separated Google Ads IDs to filter by
adGroupIdNoAd group identifier
startDateNoFilter start date
campaignIdNoCampaign identifier
entityTypeYesEntity type
locationIdYesLocation identifier
selectedAdAccountIdNoSelected ad account ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / adGroupId / example
      Previous value: -"ag_123"New value: +"123456789"
    • changedInput schema / properties / campaignId / example
      Previous value: -"camp_123"New value: +"196684453527082"
    • changedInput schema / properties / searchId / description
      Previous value: -"Search identifier"New value: +"Comma-separated Google Ads IDs to filter by"
    • changedInput schema / properties / searchId / example
      Previous value: -"search_123"New value: +"123,456"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds the concrete OAuth scope (adPublishing.readonly) and the versioned endpoint path, which is genuinely useful auth/context detail, but it says nothing about pagination, result limits, or what happens when no entities match.

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?

Compact and front-loaded: the scope sentence precedes the endpoint and scope metadata. The leading 'Get entities' line merely restates the title and could be dropped, but overall there is no padding.

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?

With full schema coverage, safety annotations, and no output schema, the remaining gap is explaining the shape of the returned entity list and how filters compose. For a read-only polymorphic getter that is a minor omission, and the description is sufficient to call it correctly.

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 both enums (type, entityType) are documented in the schema, so the description carries no parameter burden. It correctly signals that entityType selects the resource class, but adds no format, defaulting, or interaction details beyond the schema (e.g., how searchId/date filters combine).

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 names a specific verb (Retrieve) and a specific resource (Google campaigns, ad groups, or ads), and notes the selection is driven by entity type. It never names the closest sibling (ghl_ad_google_campaign_get, ghl_ad_fb_entity_get), so an agent must infer the split itself.

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 states when this polymorphic entity fetch should be chosen over the single-purpose campaign/account/integration getters in the sibling list, nor any prerequisite such as having an active Google ad integration. Usage is only implied by the phrase 'based on entity type'.

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