WebinarStack

Update Offer And Replay Basics

webinarstack.webinars.update_offer_replay_basics

Idempotent

Configure starter call-to-action and replay basics for a webinar.

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>",
      "headline": "<headline>",
      "endsAtSeconds": "<endsAtSeconds>"
    },
    "name": "webinarstack.webinars.update_offer_replay_basics"
  }
}

Input Schema

Name	Required	Default
`headline`	Yes
`timeline`	No	live
`buttonUrl`	No
`webinarId`	Yes
`buttonLabel`	No
`description`	No
`endsAtSeconds`	Yes
`replayEnabled`	No
`replayVideoUrl`	No
`appearsAtSeconds`	No
`replayExpiryDays`	No
`replayRedirectUrl`	No
`attributionWindowDays`	No
`replayRedirectEnabled`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`errors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.1/5.0

Behavior2/5

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds almost no behavioral detail beyond "Configure": it does not say which fields are affected, what happens to omitted settings, or what permissions are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and waste-free, but it is too terse for a 14-parameter configuration tool. Brevity here comes at the cost of useful structure and detail.

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

Completeness1/5

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

For a complex mutation tool with 14 parameters, 0% schema description coverage, and an output schema, the description is far too thin. It leaves the agent without the field-level meaning or usage context needed to invoke the tool correctly.

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

Parameters1/5

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

The schema has 14 parameters with 0% description coverage, and the description explains none of them. Fields such as endsAtSeconds, appearsAtSeconds, attributionWindowDays, timeline, replayExpiryDays, and replayRedirectEnabled are left entirely opaque beyond their names and types.

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

Purpose3/5

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

The description gives a specific verb (Configure) and a resource area (call-to-action and replay basics for a webinar), so the general intent is understandable. However, "starter" and "basics" are vague, and it does not distinguish this tool from close siblings such as update_replay_defaults or add_replay_with_new_offer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The sibling set contains several replay/offer-related update tools, making this omission especially costly.

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

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

Resources

Need Help?