Skip to main content
Glama

ADS Beast

analytics_media_plan

Read-only

A sourced chain of planning numbers for a campaign type: CPM, reach, clicks, CPC, conversion rate, conversions, CPA, break-even and three scenarios. Every figure is labelled with where it comes from.

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": {
      "platform": "<platform>",
      "objective_or_type": "<objective_or_type>",
      "monthly_budget": "<monthly_budget>"
    },
    "name": "analytics_media_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoBusiness niche or industry, in plain words.
currencyNoISO currency code of the budget.USD
platformYesgoogle, meta, tiktok, linkedin or microsoft.
client_idNo
num_objectsNoHow many ad sets or ad groups share the budget.
monthly_budgetYesMonthly budget in the stated currency, whole units.
avg_order_valueNoAverage order value, for revenue and break-even.
gross_margin_pctNoGross margin in percent, for break-even.
objective_or_typeYesGoal or campaign type: leads, sales, traffic, or a key from campaign_type_coverage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 genuinely useful context beyond that: every figure carries a source label (provenance), and the output includes three scenarios. It does not say whether figures are model-derived projections versus observed data, which matters for interpretation.

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 with no filler; the metric enumeration and the provenance note both earn their place. The opening is a noun phrase rather than an action statement, which slightly weakens front-loading, but nothing is redundant.

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 9-parameter computational tool with no output schema, the description must carry the return-value burden, and it does list the metrics plus the scenario count. However, it never explains what the 'three scenarios' contain, how sources are labelled, or what happens when optional inputs like avg_order_value or gross_margin_pct are omitted, leaving real ambiguity.

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?

With 89% schema description coverage, the schema already documents all nine parameters including defaults for currency and num_objects. The description hints that results are keyed to campaign type and break-even inputs, but adds no syntax, units, or fallback behavior beyond what the schema states, so the baseline of 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: a sourced chain of planning numbers for a campaign type, and enumerates the metrics produced (CPM, reach, clicks, CPC, conversion rate, conversions, CPA, break-even, three scenarios). It lacks an explicit verb (compute/estimate/derive) and never distinguishes itself from forecast or benchmark siblings, but an agent can tell what the output is.

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 guidance on when to call this versus analytics_forecast, analytics_benchmarks, or campaign_analyze, and no prerequisites are stated (e.g. that a campaign type key or AOV/margin improves output). Usage is only inferable from the metric list.

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.