Skip to main content
Glama
Sign In

AdLoop

by com.getadloop
OverviewDiscussionsAdmin

Campaigns using a negative keyword list

get_negative_keyword_list_campaigns
Read-only

List which campaigns a shared negative keyword list is attached to.

Returns each list-to-campaign attachment with the list and campaign IDs and names.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_negative_keyword_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID, digits with or without dashes (e.g. "123-456-7890"). Defaults to the configured ads.customer_id.
shared_set_idNoNumeric ID from get_negative_keyword_lists. When omitted, returns all list-to-campaign attachments across the account.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID, digits with or without dashes\n(e.g. \"123-456-7890\"). Defaults to the configured ads.customer_id."
    • addedInput schema / properties / shared_set_id / description
      Added value: +"Numeric ID from get_negative_keyword_lists. When\nomitted, returns all list-to-campaign attachments across the account."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that the result is raw list-to-campaign attachment records (IDs and names) rather than campaign objects, which is modestly useful context beyond the annotations and the output schema.

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 first sentence answers the core question, followed by a brief return-value note; nothing redundant. The trailing Google Ads API documentation link is largely filler for an agent that already has the schema and output schema.

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?

For a read-only lookup with both parameters optional, an output schema, and no nested objects, the description covers purpose and returned fields adequately. Minor omissions (pagination behavior, or that an empty result is expected when the list is unattached) do not impede correct invocation.

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 both parameters (customer_id default behavior, shared_set_id source and omit-meaning) are already fully documented in the schema. The description adds no parameter syntax or format details, 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 (list) and a precise resource (which campaigns a shared negative keyword list is attached to), which is naturally distinguishable from get_negative_keyword_lists and get_negative_keyword_list_keywords. It never names those siblings explicitly, so an agent gets no direct differentiation beyond the topic wording.

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?

The description offers no when-to-use guidance, no prerequisite (e.g. needing a shared_set_id from get_negative_keyword_lists), and no alternatives. The only usage hint - that omitting shared_set_id returns everything - lives in the input schema, not here.

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

All AdLoop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources