KrystalView Analytics

Get Campaign ROAS

get_campaign_roas

Read-onlyIdempotent

Get paid campaign spend, clicks, sessions, attributed conversions, and ROAS where ad data is connected.

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

Input Schema

Name	Required	Description	Default
`days`	No	Lookback period in days.

Output Schema

Name	Required	Description	Default
`data`	Yes	Paid campaign spend, clicks, sessions, conversions, revenue, and ROAS evidence where connected.
`meta`	Yes	Site and rate-limit metadata for the current MCP call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint true and idempotentHint true, indicating safe, non-destructive behavior. The description adds the non-obvious requirement that ad data must be connected, which is useful for the agent to avoid errors.

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?

Single sentence of 18 words, front-loaded with the key action and outputs, and no filler. Every word contributes meaning.

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

Completeness5/5

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

Given the presence of an output schema, full parameter schema coverage, and comprehensive annotations, the description's concise mention of data dependency and metric list is sufficient for the agent to understand tool behavior and prerequisites.

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 coverage is 100%, so the schema fully documents the 'days' parameter. The description does not add any extra semantic detail beyond the schema, resulting in baseline score of 3.

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?

Description clearly states it retrieves specific paid campaign metrics (spend, clicks, sessions, attributed conversions, ROAS) when ad data is connected. This distinguishes it from sibling tools like get_campaign_sessions (likely sessions only) and get_campaign_summary (broader summary).

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?

The description provides clear context by listing the exact metrics returned and the prerequisite (ad data connected). It does not explicitly state when not to use it, but the clarity of its purpose implicitly guides the agent away from using it for non-paid campaign data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All KrystalView Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.