Skip to main content
Glama

ADS Beast

creative_banner_quality_check

Read-only

Reviews a generated banner of ADS Beast for garbled text, legibility, platform spec fit and visual quality, with a score and fixes. 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": {
      "creative_id": "<creative_id>"
    },
    "name": "creative_banner_quality_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNometa
creative_idYesADS Beast creative id, as returned by prepare_banner_generate once it ran.
format_labelNoFormat label, for example 'Feed 1:1' or 'Story 9:16'.

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 cover the safe-read profile (readOnlyHint true, destructiveHint false), and the description adds information they don't: the run time (up to a minute), the AI-request cost, and the shape of the result (a score plus suggested fixes). It does not detail failure modes or what happens if the creative_id is missing or unready, but the added context is solid beyond the annotations.

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 tight sentences, with the core purpose front-loaded and cost/latency trailing. "AI: 1 AI request" is terse and slightly awkward but conveys useful pricing context rather than filler.

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 no output schema, the description correctly compensates by stating the result is a score with fixes, and it discloses expected latency. The main residual gap is differentiation from sibling analysis/quality tools, which is a routing concern rather than a completeness one.

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 67% and the schema already documents creative_id and format_label with examples; the enum on platform is self-explanatory. The description only hints at the platform parameter via "platform spec fit" and adds no syntax or default information beyond the schema, so 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?

"Reviews a generated banner of ADS Beast" states a specific verb and resource, and the list of checks (garbled text, legibility, platform spec fit, visual quality) makes the scope concrete. It stops short of naming or contrasting a sibling such as creative_image_analyze, so an agent must infer why to pick one over the other.

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 use after banner generation, and the schema's creative_id note ("as returned by prepare_banner_generate") reinforces the ordering prerequisite. However, there is no explicit statement of when to use this versus sibling quality/analysis tools, or when not to call it.

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.