Skip to main content
Glama

ADS Beast

audit_campaign_health

Read-only

A 1-10 health score for each campaign of a client with the problems behind it.

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_campaign_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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. The description adds useful return-shape context (a 1-10 score plus the problems behind it) that annotations do not provide, but it says nothing about coverage of campaigns, scoring criteria, or behavior when a client has no campaigns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so nothing is wasted, but it is a noun-phrase fragment without a verb and provides no front-loaded action statement. Brevity here reflects under-specification rather than disciplined conciseness.

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?

The tool is simple (one required parameter, no nested objects, no output schema), and the description does sketch the return value, which is the right thing to cover when no output schema exists. However, it omits how campaigns are covered and what the score is based on, leaving an agent without enough to interpret results confidently.

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 0% for the single required client_id, but the description's phrase 'of a client' does confirm that client_id scopes the audit to one client's campaigns, adding a small amount of meaning. It gives no format, range, or validation detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the output of the tool (a 1-10 health score per campaign plus the underlying problems) but never names the action with a verb, and it does not distinguish itself from near-neighbors like audit_campaign_quality, audit_campaign_portfolio, or analytics_kpi_health. An agent can infer it is an audit-style read that returns scored results, but the specific scope is only loosely conveyed.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, despite the sibling list containing several overlapping campaign/health/quality audits. The only implicit guidance is the phrase 'of a client', which hints at per-client scoping but nothing more.

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.