Skip to main content
Glama

ADS Beast

google_ads_conversion_tracking_check

Read-only

Reads a client's Google Ads conversion actions and tag and reports which action fits the named conversion, or what would be created. Read-only.

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": "<name>"
    },
    "name": "google_ads_conversion_tracking_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesConversion name, for example 'CRM signup'.
categoryNoConversion category.SIGNUP
client_idYes
account_idNoGoogle account id; needed only when the client has several.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Read-only' sentence adds nothing new. It does add useful context that the tool reports either a matching existing action or a projected creation outcome, but it says nothing about what happens when no action matches, how the tag is inspected, or any permission requirements.

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 compact sentence with the action verb and resource front-loaded and no filler. It could only be improved by replacing the redundant 'Read-only' tail with routing guidance toward the sibling create tool.

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?

With no output schema, the description bears responsibility for explaining return values; it gestures at the outcome ('which action fits... or what would be created') but does not describe the shape of the report or the no-match case. For a four-parameter check tool this is adequate but not complete.

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 coverage is 75% and already documents name, category (with enum and default), and account_id's conditional use; client_id is undocumented in both places, though 'a client's' weakly implies it. The description adds no meaning about how name matching is performed (exact vs fuzzy) or how category affects the fit decision.

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 uses a specific verb and resource ('Reads a client's Google Ads conversion actions and tag') and states the outcome ('reports which action fits the named conversion, or what would be created'). An agent can distinguish this reconnaissance call from the audit_* family, though it never names a sibling explicitly.

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?

The phrase 'or what would be created' implies this is a pre-flight check before prepare_google_conversion_action_create, but the relationship is left to inference rather than stated. No explicit when-to-use, when-not-to-use, or prerequisite guidance is given.

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.