The Marketing Vault

Write a webinar

write_webinar

Creates webinar scripts, presentation ideas and titles, model recommendations or presentation audits. Output is saved to the Library and uses one generation. Nothing is sent or published.

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": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "write_webinar"
  }
}

Input Schema

Name	Required	Description
`details`	Yes	What the user wants, including supplied source text, goals or constraints.
`template`	Yes	full-webinar-script: Write a complete webinar presentation script. presentation-concepts: Develop presentation ideas, titles and concepts. enhance-title: Improve a presentation title. choose-presentation-model: Recommend a one-to-many presentation model. high-level-audit: Audit an existing presentation at a high level. detailed-audit: Audit an existing presentation in detail.
`business_context`	No	Business context for the selected template.
`business_profile_id`	No	Business profile id. Required when the account has multiple Businesses.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=false, so the description's job is to add context—and it does: output goes to the Library, it consumes one generation (a credit/cost signal not in the schema), and nothing is sent or published. That credit consumption note is genuinely useful behavioral information absent from structured fields.

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 sentences, front-loaded with the verb and deliverables, followed by the storage and cost caveats. Every clause carries information and none is redundant.

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, fully documented schema with no output schema, the description covers what the tool produces, where the result lives, and that it is non-destructive. The only gap is whether the generated content is also returned inline versus only persisted to the Library.

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%, with the template enum fully self-documenting and details/business_context already explained. The description adds essentially nothing about parameter meaning beyond echoing the template categories, so the baseline 3 applies.

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?

The description opens with a specific verb and resource: 'Creates webinar scripts, presentation ideas and titles, model recommendations or presentation audits.' The enumerated artifact types map cleanly onto the six template enum values, so an agent can tell this is the webinar-specific generator versus write_blog_article or write_email_copy. It stops short of explicitly naming those siblings, which keeps it at 4.

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?

Usage is implied by the artifact list and by the note that output is saved to the Library rather than sent, but there is no explicit 'use this when...' or exclusion against the other write_* tools. An agent must infer that a webinar request routes here and unrelated copy routes elsewhere.

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

All The Marketing Vault 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?