Skip to main content
Glama

ADS Beast

creative_prompt_templates

Read-only

A library of prompts for generating ad banners, filtered by business vertical and visual style.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "creative_prompt_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoVisual style.
verticalNoBusiness vertical.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description does add one genuinely useful behavioral fact beyond that: this is a static library lookup, not a generation call. It omits how many templates come back, how results are ordered, and what an unfiltered call returns.

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?

One sentence, front-loaded with the resource, with the filtering dimension appended. Nothing is redundant or padded, and it is short enough to be read at a glance.

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?

With zero required parameters and no output schema, the description should say what an unfiltered call returns and roughly what a template entry looks like. It conveys the concept of a prompt library adequately for a simple two-filter tool but leaves the return shape entirely undocumented.

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 coverage is 100% and both parameters are enums with inline descriptions, so the schema carries the burden. The description's only added signal is that the two parameters act as filters, which slightly clarifies that they narrow a library rather than select a single template; no format or default behavior is explained.

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?

"A library of prompts for generating ad banners" names the resource being retrieved and the domain, making it clear this returns prompt templates rather than generating images or copy. It does not distinguish itself from adjacent siblings such as creative_copy_generate or creative_image_analyze, so an agent must infer that this is the pre-generation lookup step.

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 when-to-use statement, no prerequisites, and no named alternative. The mention of filtering "by business vertical and visual style" hints at how to narrow results but never says when this tool should be chosen over the copy or image tools in the sibling list.

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.