Skip to main content
Glama

ADS Beast

audit_campaign_portfolio

Read-only

Health score of every campaign, the ones in a critical state, without conversions, without goals or with stale data. A good first call before a deeper audit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_campaign_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo
only_activeNoOnly running campaigns.

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, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds useful triage context about what conditions get flagged (critical, no conversions, no goals, stale data), but says nothing about result volume, pagination, or how the health score is computed or scaled.

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?

Two short sentences, front-loaded with what the tool returns and closed with the sequencing hint. The first sentence is a noun phrase rather than a full clause, which slightly reduces immediate readability but costs no length.

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 two-parameter read-only triage tool with no output schema, the description is adequate but leaves the agent guessing about the response shape (one row per campaign? score scale?) and about the undocumented client_id. An agent can call it, but not predict its output.

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?

Schema description coverage is only 50% – only_active is documented in the schema, while client_id is not. The description mentions neither parameter, so it fails to compensate for the undocumented client_id and gives no hint about the default-true active-only scoping.

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 the resource (every campaign) and the specific outputs it surfaces: health score, critical state, missing conversions, missing goals, stale data. That is concrete enough to distinguish it from a single-campaign check like audit_campaign_health, though it stops short of explicitly naming a sibling to contrast with.

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

Usage Guidelines4/5

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

'A good first call before a deeper audit' gives clear sequencing guidance and implicitly routes the agent to the deeper audit tools for follow-up. It does not state any when-not or exclusions, so it falls short of a 5.

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.