Skip to main content
Glama

ADS Beast

google_ads_ad_strength

Read-only

Ad Strength of a client's responsive search ads: counts by level and the weak ads with Google's own action items.

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": {
      "client_id": "<client_id>"
    },
    "name": "google_ads_ad_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
force_refreshNotrue queries Google live instead of using the stored snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added value is the disclosure of what comes back — per-level counts plus flagged weak ads with Google's own recommendations. That return-content statement is genuinely useful because no output schema exists; it omits only caching/live-query behavior, which the schema field already explains.

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?

A single front-loaded sentence with no filler, and the resource is named before the returned payload. It is dense but readable and every clause carries information.

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?

For a simple two-parameter read tool with annotations supplying the safety profile, describing the return content is close to sufficient. However, it leaves an agent guessing what to do with weak ads (which sibling fixes them) and what client_id expects, so it is adequate rather than complete.

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

Parameters2/5

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

The description mentions no parameters at all. Schema coverage is 50%: force_refresh is documented as a live-vs-snapshot switch, but client_id has no description, and the definition does not clarify that it is the internal client identifier rather than a Google Ads customer ID. At this coverage level the description should have compensated and does not.

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 resource and metric ('Ad Strength of a client's responsive search ads') plus the payload shape ('counts by level and the weak ads with Google's own action items'), so an agent knows this is a diagnostic read, not a mutation or an audit sweep. It does not explicitly contrast itself with nearby siblings such as google_ads_keyword_overlap or audit_google_ads, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'weak ads with action items' hints at a remediation workflow, but the description never says when to call this versus running a full audit or generating RSA variations with a sibling like prepare_google_rsa_variations. No exclusions or prerequisites are stated.

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.