Skip to main content
Glama

ADS Beast

leads_quality_diagnose

Read-only

Works out where a campaign loses lead quality and what to change, from the numbers and complaints supplied. Takes up to a minute. Amounts are in the ad account's own currency, in whole units (not cents or micros). AI: 1 AI request. May return a job_id (get_job_result).

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": {
      "campaign_name": "<campaign_name>",
      "platform": "<platform>"
    },
    "name": "leads_quality_diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpaNoActual cost per lead.
ctrNoCTR in percent.
spendNoSpend over the period.
clicksNoClicks over the period.
platformYes
client_idNoClient id; when given, the result is saved as a report.
target_cpaNoTarget cost per lead.
conversionsNoConversions over the period.
campaign_nameYesCampaign name.
lead_complaintsNoWhat is wrong with the leads, in the client's words.
landing_page_urlNoLanding page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 safety is covered. The description adds genuinely new behavioral facts beyond them: the call can take up to a minute, consumes one AI request, and may return a job_id that must be polled via get_job_result — all of which materially affect how an agent should invoke and follow up.

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 core purpose is front-loaded in the first sentence, followed by short, independently useful facts about latency, currency units, AI cost, and async retrieval. The fragment style ('AI: 1 AI request.') is terse but readable; no sentence is padding, though the presentation is slightly telegrammatic rather than flowing.

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 an 11-parameter, no-output-schema tool, the description covers the essentials an agent needs: what it computes, input expectations, runtime, currency units, cost, and the possible job_id follow-up path. It does not describe the shape of the returned diagnosis or confirm that most numeric metrics are optional, which is the main remaining gap.

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 coverage is 91%, so the baseline is 3 and the schema already explains most fields. The description adds real semantic value by specifying that monetary amounts (spend, cpa, target_cpa) are in the ad account's own currency in whole units, not cents or micros — a unit convention the schema does not state and one that would cause silent errors if assumed wrong.

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 gives a specific verb and resource: it diagnoses where a campaign loses lead quality and prescribes what to change, based on supplied metrics and complaint text. The purpose is unambiguous, but it never distinguishes itself from near-name siblings such as campaign_diagnose or audit_campaign_quality, leaving the agent to infer the boundary.

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 implied by 'from the numbers and complaints supplied', which tells the agent this tool wants metric inputs plus qualitative complaint text. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative for adjacent diagnoses, so the agent must infer the routing decision.

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.