Skip to main content
Glama

The Marketing Vault

Design an offer

design_offer

Designs or audits offers, sales-call offers and value ladders. 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": "design_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsYesWhat the user wants, including supplied source text, goals or constraints.
templateYesoffer-architect-audit: Design or audit a paid or no-cost offer. webinar-vsl-offer: Design an offer for a webinar or VSL. sales-call-offer: Design a no-cost sales-call offer. value-ladder-intelligence: Analyze value ladder opportunities. value-ladder-architecture: Design a value ladder from prior intelligence. value-ladder-rollout: Plan rollout of a validated value ladder.
paid_offerNoPaid offer for the selected template.
call_formatNoCall format for the selected template.
constraintsNoConstraints for the selected template.
ladder_intelNoMonetization intelligence from value ladder step 1.
naming_styleNoNaming style for the selected template.
business_contextNoBusiness context for the selected template.
validated_ladderNoValidated value ladder from the previous step.
existing_call_nameNoExisting call name for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.
presentation_contextNoPresentation context for the selected template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and idempotentHint=false, but the description adds genuinely new behavioral facts: the result is persisted to the Library and consumes one generation. The sentence "Nothing is sent or published" usefully bounds the side-effect surface for a non-read-only 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, zero filler, with the capability statement first and the persistence/cost/no-publication facts second. Nothing is repeated from the schema or annotations.

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

Completeness3/5

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

For a 12-parameter tool with template-conditional fields, the description omits how the optional inputs map to each template and does not repeat the schema's note that business_profile_id is required for multi-business accounts. It does cover the output destination and generation cost, and no output schema exists to offload return-value explanation, leaving a moderate 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%, including a fully annotated template enum, so the schema already carries the parameter meaning and the description rightly does not repeat it. It adds no guidance on how the many template-specific fields (paid_offer, ladder_intel, validated_ladder) relate to the chosen template, so the baseline 3 is appropriate.

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?

"Designs or audits offers, sales-call offers and value ladders" gives specific verbs (design, audit) and named resources, so the agent knows exactly what class of artifact this produces. It does not distinguish itself from nearby siblings like write_sales_scripts or improve_existing_copy, which is the only thing keeping it from a 5.

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 verb set — you invoke this when you want an offer or value ladder built or reviewed — but there is no explicit when-to-use statement, no when-not-to-use statement, and no named alternative for overlapping tasks such as improving existing copy or writing sales scripts.

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