Skip to main content
Glama
Sign In

WebinarStack

by co.webinarstack
OverviewDiscussionsAdmin

Add Replay with New Offer

webinarstack.workflows.add_replay_with_new_offer

Configure replay availability and attach an alternative offer on the replay timeline of an existing webinar in one call. Enables replay, sets replay expiry/video/redirect settings, and creates or updates a replay-timeline CTA interaction with the supplied offer fields. The replay CTA is find-or-created by the underlying service (one CTA per timeline). Returns { webinarId, replayEnabled, offerInteractionId, interactionCount, steps }.

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": {
      "webinarId": "<webinarId>",
      "offer": "<offer>"
    },
    "name": "webinarstack.workflows.add_replay_with_new_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerYesAlternative offer to display on the replay timeline
replayNoReplay availability settings
webinarIdYesID of the existing webinar to configure replay and offer on
interactionsNoAdditional replay-only CTA interactions (note: only the single offer CTA is currently supported via updateOfferReplayBasics; additional interactions will be noted as skipped)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-idempotent, non-destructive), the description discloses the key behavioral trait that the CTA is find-or-created by the underlying service with one CTA per timeline, which explains why repeats mutate rather than duplicate. It also enumerates the concrete return shape even though no output schema exists; it does not state permission requirements or what happens to pre-existing replay settings.

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 sentences, front-loaded with the operation, then behavior, then return shape; no filler or restated title text. The return-value sentence replaces an absent output schema efficiently.

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 4-parameter composite mutation with nested objects and no output schema, the description covers intent, side effects, find-or-create semantics, and the response shape. It stops short of covering prerequisites/authorization and the effect on existing replay or CTA configuration, which is 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 description coverage is 100%, so per-parameter meaning is already carried by the schema (including the note that extra interactions are skipped). The description adds the important cross-parameter constraint 'one CTA per timeline' but does not otherwise explain how the replay object fields interact or which take precedence over webinar-level defaults.

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 composite verb set ('Configure replay availability and attach an alternative offer') on a concrete resource ('replay timeline of an existing webinar') and explicitly frames it as a bundled 'in one call' operation, which separates it from the narrower sibling tools update_offer_replay_basics and update_replay_defaults.

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 phrase 'in one call' hints at the bundled use case and 'existing webinar' implies a prerequisite, but there is no explicit when-to-use/when-not-to-use guidance and no named alternatives such as update_offer_replay_basics or webinarstack.webinars.update_replay_defaults for partial updates.

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

All WebinarStack toolsInspect
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.

Resources