Skip to main content
Glama

save_sulvo_advanced_report

Destructive

Create/update a Sulvo advanced report (adUnit, dimensions, or customData), run immediately (emailed) or on a recurring schedule. Requires SULVO_API_KEY (with the reports:write scope) in the server environment. Note: advanced reports are delivered by email, not returned inline.

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": {
      "reportType": "<reportType>",
      "toAddress": "<toAddress>",
      "immediateRun": "<immediateRun>"
    },
    "name": "save_sulvo_advanced_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
nameNo
utmsNocustomData (UTM) reports only.
startNo
adRootsNo
domainsNo
reportIdNoProvide to update an existing saved report.
timeZoneNoIANA timezone for scheduled delivery.
frequencyNoRequired when immediateRun is false.
toAddressYesEmail address the report is delivered to.
dimensionsNo
reportTypeYesAdvanced report type.
immediateRunYestrue to run now (emailed), false to only schedule (requires frequency).
outputFormatNomarkdown
utmHourlyBreakdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / toAddress / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the description only needs to add context. It does so meaningfully: it discloses the required API key scope and, crucially, that output is emailed rather than returned inline — a behavioral trait an agent cannot infer from the schema. It does not explain what an update overwrites on an existing report, which is the main gap given destructiveHint=true.

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?

Three tight sentences, front-loaded with the action, then the prerequisite, then the delivery caveat. Nothing is redundant and every sentence carries information the agent needs.

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?

With no output schema, the description correctly closes the biggest gap by stating that reports are emailed and not returned inline. However, for a 15-parameter, destructive, open-world mutation, it does not explain per-reportType field requirements or what an update to an existing reportId replaces, leaving real ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 47% across 15 parameters, so the description must compensate, but it mostly restates what the schema already says (reportType values, immediateRun vs. frequency). Parameters such as adRoots, domains, start/end, utms, timeZone, outputFormat and utmHourlyBreakdown receive no clarification, and the description does not indicate which fields are required or meaningful per reportType.

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?

Names a specific verb pair (create/update) and resource (Sulvo advanced report) and enumerates the three report subtypes (adUnit, dimensions, customData), which helps distinguish it from list_sulvo_advanced_reports and delete_sulvo_advanced_report. It stops short of explicitly routing the agent away from get_sulvo_report, 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?

The description conveys two usage modes (run now vs. scheduled) and a prerequisite (SULVO_API_KEY with reports:write scope), which is useful context. It never states when to prefer this tool over get_sulvo_report or list_sulvo_advanced_reports, nor when an agent should update an existing report vs. create a new one.

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