Skip to main content
Glama

ADS Beast

creative_copy_generate

Generate ad variants (headlines, texts, calls to action) for a client and save them as drafts. Takes up to a minute. AI: 1 AI request.

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": {
      "client_id": "<client_id>",
      "platform": "<platform>"
    },
    "name": "creative_copy_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoTone of voice.professional
countNoNumber of variants.
ad_typeNosearch, display, video, stories or feed.feed
platformYes
client_idYes

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 already declare this is a non-destructive write to an open-world system, so the safety bar is covered. The description adds genuinely non-schema behavior: results are persisted as drafts rather than published, the call can take up to a minute (latency expectation), and it consumes one AI request (cost budget). It does not say whether drafts attach to a specific campaign or how they can be retrieved afterward.

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

Conciseness4/5

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

Three short sentences with the core action front-loaded; the latency and AI-cost notes are terse but earn their place by informing the agent's timing and budget decisions. The fragment 'AI: 1 AI request' is slightly cryptic but not wasteful.

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?

With five parameters, two required, no output schema, and annotations covering the safety profile, the description covers the essentials: what is produced, that it is saved rather than published, and the expected duration and cost. A brief note on what is returned (e.g., draft identifiers) would close the remaining gap left by the absent output 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 60%, with tone, count, and ad_type documented but client_id and platform bare. The description adds only a weak hint that copy is scoped to a client; it says nothing about how tone, count, or ad_type shape the output, so the schema still carries most of the meaning. 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?

The description gives a specific verb ('Generate') and resource ('ad variants') and enumerates the artifact types produced (headlines, texts, calls to action), plus the side effect that they are saved as drafts. It does not explicitly contrast with siblings such as creative_copy_humanize or creative_prompt_templates, so it stops short of 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: this is the tool for producing fresh ad copy for a client. There is no explicit statement of when to prefer it over alternatives like humanize or template-based tools, and no prerequisites or exclusions are given.

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.