Skip to main content
Glama

ADS Beast

audit_conversion_goals

Read-only

Check that a client's ads learn from real leads: which Google Ads conversions are primary, whether calls and forms are counted, and campaigns optimising for the wrong goal.

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": "audit_conversion_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds the audit's inspection scope, which helps interpret results, but says nothing about whether it queries live ad platforms, how long it takes, or what happens when a client has no Google Ads linkage.

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?

One sentence, front-loaded with the verb and intent, with no filler. The colon-delimited checklist keeps the detail scannable, though the opening 'ads learn from real leads' framing is slightly indirect compared to simply stating 'audit conversion goal configuration'.

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, single-parameter audit with annotations covering safety, the description gives enough to select and call it correctly, and it implicitly bounds scope to Google Ads. The main unstated elements are the result shape (no output schema exists) and any prerequisites for a meaningful audit.

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?

There is a single required parameter, client_id, which is self-evident from its name; the description frames it implicitly as 'a client's ads'. Schema description coverage is 0%, but with one unambiguous integer identifier there is little semantic gap left to close.

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 ('Check') and a clearly bounded resource (conversion goals for a client's Google Ads), then enumerates the three things it evaluates: which conversions are primary, whether calls and forms are counted, and campaigns optimising for the wrong goal. It is distinguishable from nearby siblings such as audit_tracking or google_ads_conversion_tracking_check, though it never names an alternative.

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: an agent can infer this is for diagnosing conversion-goal misconfiguration, and the phrase 'learn from real leads' hints at the optimisation-mismatch use case. There is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., account must be linked to Google Ads) 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.