Skip to main content
Glama

Honeyfield Marketing MCP

DataForSEO: Google ads advertisers

dfs_google_ads_advertisers
Read-only

Werbetreibende, die laut Google Ads Transparency Center fuer dieses Keyword Anzeigen schalten — Wettbewerbs-Ueberblick jenseits der aktuell aktiven SERP-Anzeigen. location/language: Default aus dem Workspace; Format wie bei dfs_keyword_volume. Fehler kommen als Ein-Element-Liste [{error, ...}] (api_error/task_error, dfs_timeout, dfs_unreachable) — vor der Auswertung auf 'error' pruefen. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "keyword": "<keyword>"
    },
    "name": "dfs_google_ads_advertisers"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes
languageNo
locationNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond that: location/language default from the workspace, workspace is optional when only one exists, and errors are returned as a one-element list that must be checked before evaluation.

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?

The description is front-loaded with the core purpose and then moves to defaults, error handling, and workspace semantics. It is somewhat dense, but each clause contributes operational information.

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?

An output schema exists, so return values need not be explained. The description covers the required keyword, default location/language behavior, workspace selection, and error shape, leaving only minor format details implicit through the dfs_keyword_volume reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden. It explains all four parameters at a practical level: keyword scope, location/language defaults and format reference via dfs_keyword_volume, and workspace as an optional customer slug.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and source: advertisers running ads for a keyword according to the Google Ads Transparency Center. It also distinguishes the scope from 'aktuell aktiven SERP-Anzeigen', so an agent can tell this is a competitive transparency lookup rather than an active-SERP ad query.

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?

The first sentence gives a clear usage context: competitive overview beyond currently active SERP ads. It does not explicitly name the alternative sibling or say when not to use this tool, but the intended use case is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources