Skip to main content
Glama

create_sulvo_interstitial_units

Create Sulvo interstitial ad units (tagless) for an approved publisher. Requires SULVO_API_KEY (with the inventory:write scope) in the server environment.

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": {
      "domain": "<domain>",
      "adTypes": "<adTypes>"
    },
    "name": "create_sulvo_interstitial_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublisher domain the units belong to.
adTypesYesOne or more interstitial ad types to create.
outputFormatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as a non-destructive, non-open-world write, so the description's job is additive — and it delivers by naming the required SULVO_API_KEY with the inventory:write scope and the publisher-approval prerequisite. It doesn't cover idempotency or whether re-creating an existing domain/adTypes pair fails, which would be the remaining gap for a write tool.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the environment prerequisite. Every clause carries actionable information.

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 three-parameter mutation with annotations covering side-effect profile and no output schema, the description supplies the two things structured fields cannot: auth scope and publisher-approval gating. A note on duplicate handling or what the units look like on return would close the remaining gap.

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 67%: domain and adTypes are documented in-schema, while outputFormat has no description anywhere. The description's 'interstitial' wording loosely maps to the adTypes enum values but adds no format, default, or multi-unit behavior guidance beyond the schema.

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?

States a specific verb and resource — creating Sulvo interstitial ad units — plus the qualifier 'tagless', which separates it from create_sulvo_ad_unit and create_sulvo_auto_sticky_units. It doesn't explicitly name those siblings, so differentiation is inferred from the ad-type rather than directed.

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?

'for an approved publisher' establishes a real precondition an agent must satisfy before calling. However, it never says when to prefer this over create_sulvo_ad_unit or create_sulvo_auto_sticky_units, nor what to do when no interstitial inventory is needed.

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