Skip to main content
Glama

ADS Beast

meta_ads_learning_phase

Read-only

Learning status of every active ad set of a client, with what holds learning back.

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": "meta_ads_learning_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
campaign_idNoMeta's own campaign id, to check one campaign only.
target_cpa_usdNoTarget CPA, used to judge whether budgets are sufficient.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint). The description adds real context beyond them: scope is limited to active ad sets (paused ones excluded) and the response includes the blockers holding learning back, which matters because no output schema exists. It does not mention API cost, latency, or access requirements, keeping it short of a 5.

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?

One short sentence with the scope front-loaded and no filler. It is telegraphic rather than well-formed prose, which slightly hurts readability but not efficiency.

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 read-only, three-parameter tool with no output schema, the description covers scope and result content adequately. It leaves the effect of target_cpa_usd and the response structure (per-ad-set list, formatting) unexplained.

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 67% and campaign_id and target_cpa_usd both carry inline explanations, so the schema does most of the work. The description adds nothing about how target_cpa_usd affects the judgment or whether campaign_id narrows the result set, so baseline 3 applies.

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 a specific resource (learning status of every active ad set) and adds the diagnostic angle ('what holds learning back'), so an agent knows this is a learning-phase diagnostic, not a general audit. It omits an explicit verb and does not name any sibling such as audit_meta_ads, so it is clear but not differentiated.

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 or when-not-to-use guidance and no mention of alternatives like audit_meta_ads or meta_ads_account_setup. The diagnostic framing implies a use case, but the agent must infer it entirely.

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.