Skip to main content
Glama

ADS Beast

recommendation_save

Record a recommendation so ADS Beast checks in seven days whether it worked.

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": {
      "action": "<action>",
      "metric": "<metric>"
    },
    "name": "recommendation_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat was recommended.
metricYesThe metric expected to improve.
client_idNo
reasoningNoWhy it should work.
campaign_idNoADS Beast id from list_campaigns, not the platform's.
target_valueNoIts expected value afterwards.
current_valueNoIts value now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, but the description adds genuine behavioral context the annotations cannot: the record is later evaluated automatically after seven days, making this a write with a delayed verification consequence. It still omits what is returned and whether repeat saves for the same campaign create duplicates.

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

Conciseness5/5

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

A single sentence with no filler, front-loading the action and immediately stating the downstream consequence. Nothing could be removed without losing information.

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 7-parameter mutation tool with no output schema, the definition covers the core intent but leaves open what is returned, whether re-saving the same campaign/metric overwrites or duplicates, and what data source feeds the seven-day check. Adequate but with real gaps for a write operation.

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 86%, so the schema already explains action, metric enum, campaign_id provenance and current/target values. The description adds only the framing that 'worked' is judged against a metric — nothing about formatting, units, or how current_value and target_value interact. Baseline 3 is appropriate.

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 ('Record a recommendation') plus the distinctive outcome ('ADS Beast checks in seven days whether it worked'), which distinguishes it from the list-style sibling recommendation_list. It stops short of naming an alternative, so it is clear but not fully differentiated.

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 infers it should call this after making a recommendation that should be tracked. There is no explicit when-to-use, when-not-to-use, or prerequisite (e.g. whether the campaign must already exist or whether duplicates are rejected).

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.