Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Analyse a sponsored-ads search-term report

ecommerce-profitability_ppc-report-analyze
Read-onlyIdempotent

Aggregate ACoS, ROAS, TACoS, CTR and CVR for a search-term report and flag negate, promote and insufficient-data candidates from caller rules. Price $0.04 USDC. POST /api/v1/ecommerce-profitability/ppc-report-analyze. An unpaid call returns the x402 payment terms and does not run.

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": {
      "currency": "<currency>",
      "rows": "<rows>",
      "totalSales": "<totalSales>",
      "rules": "<rules>"
    },
    "name": "ecommerce-profitability_ppc-report-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesrows, array. Required.
rulesYesrules, object. Required.
currencyYescurrency, string, length 3 to 3. Required.
totalSalesYesspend, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
negateNonegate. Array.
totalsNototals. Object.
promoteNopromote. Array.
sourcesNosources. Array.
currencyNocurrency. String.
limitationsNolimitations. Array.
wastedSpendNowastedSpend. Number.
insufficientDataNoinsufficientData. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), but the description adds material behavior: the $0.04 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms and does not execute. That payment-gating disclosure is the kind of context structured fields do not carry.

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?

Three sentences, front-loaded with purpose, followed by price/endpoint and the payment-gating caveat. Little waste, though the raw endpoint path is somewhat redundant given the tool name; overall tight and well ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object tool with an output schema, the description needn't explain return values, and it covers purpose, cost, and the paywall behavior. The only gap is explicit guidance on alternatives and rule semantics, which keeps it just short of a 5.

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 100%, so the schema already documents all four required parameters including the nested rows fields and rules thresholds. The description's reference to 'caller rules' loosely ties to the rules object but adds no syntax, defaults, or semantics beyond what the schema provides, making baseline 3 appropriate.

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

Purpose5/5

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

States a specific verb and resource: 'Aggregate ACoS, ROAS, TACoS, CTR and CVR for a search-term report and flag negate, promote and insufficient-data candidates from caller rules.' The metrics, the input artifact (search-term report), and the output classifications are all named, so an agent can distinguish it from pricing or cost siblings without opening the schema.

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?

The description implies usage (analyze a search-term report against caller-supplied rules) and clarifies the payment precondition for running. However, it names no alternative tool or explicit 'when not to use' condition, so an agent must infer that this is the right tool for PPC term analysis from the purpose text alone.

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.

Resources