The Marketing Vault

Write sales scripts

write_sales_scripts

Creates high-ticket sales-call frameworks or direct-message and text sales scripts. 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_sales_scripts"
  }
}

Input Schema

Name	Required	Description
`offer`	No	Offer for the selected template.
`price`	No	Price for the selected template.
`details`	Yes	What the user wants, including supplied source text, goals or constraints.
`business`	No	Business for the selected template.
`platform`	No	Platform for the selected template.
`template`	Yes	high-ticket-sales-call: Write a high-ticket sales-call framework. dm-text-close: Write direct-message and text close scripts.
`proof_assets`	No	Proof assets for the selected template.
`offer_details`	No	Offer details for the selected template.
`icp_description`	No	Icp description for the selected template.
`business_context`	No	Business context for the selected template.
`business_profile_id`	No	Business profile id. Required when the account has multiple Businesses.
`named_session_details`	No	Named session details for the selected template.

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?

Beyond the annotations, it discloses two things the agent cannot see elsewhere: the output is persisted to the Library and the call consumes exactly one generation, and nothing is externally published. This complements destructiveHint=false and openWorldHint=false with useful cost and side-effect context, though it doesn't explain failure or duplicate-call behavior despite idempotentHint=false.

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 the capability stated first and the cost/side-effect constraints second. Every clause carries information an agent needs; nothing is redundant with the title or schema.

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 12-parameter generation tool with no output schema, the definition covers what is produced, where it goes, and that it is non-publishing and single-generation. The remaining gap is that it doesn't clarify how the template choice governs which optional fields matter, leaving that to the schema.

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 the schema already documents all 12 parameters including the template enum. The description only echoes the two template variants and adds no field-level meaning such as how optional per-template fields (offer, proof_assets, icp_description) interact with the selected template.

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?

"Creates high-ticket sales-call frameworks or direct-message and text sales scripts" gives a specific verb (creates) plus the two concrete artifacts, matching the template enum values. It is clearly distinct from write_email_copy or write_blog_article, though it never names a sibling to reinforce the boundary.

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 implies usage (choose one of two script formats, output lands in the Library, nothing is sent) but gives no explicit when-to-use or when-not-to-use guidance relative to the other write_* tools. An agent must infer that DM/text closing scripts belong here rather than in write_email_copy.

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?