Skip to main content
Glama

ADS Beast

creative_image_analyze

Read-only

Reviews an ad image for platform fit, visual hierarchy, call-to-action legibility and brand fit. 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": {
      "image_url": "<image_url>"
    },
    "name": "creative_image_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoBrand, audience or goal.
platformNo
image_urlYesPublic https URL of the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact -- 'AI: 1 AI request' signals a metered model call -- but says nothing about latency, output shape, or what happens when the image is inaccessible.

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?

Two short sentences with the evaluation axes front-loaded and no filler. The 'AI: 1 AI request' fragment is terse to the point of being slightly cryptic, but it earns its place as a cost signal.

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?

There is no output schema, so the description would ideally sketch what a review returns (scores, findings, recommendations). It specifies inputs and evaluation dimensions but leaves the response shape entirely unspecified, which is an appreciable gap for an analysis tool.

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%, so most parameters are already documented, and the description implicitly ties 'platform fit' to the platform enum and 'brand fit' to the context string. It adds that interpretive link but no format or constraint details beyond the schema's 'Public https URL' note.

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?

States a specific verb (reviews) and resource (an ad image) and enumerates the four evaluation axes: platform fit, visual hierarchy, CTA legibility, brand fit. That is far more concrete than a tautology. It does not distinguish itself from close siblings like creative_banner_quality_check, 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 by the listed evaluation dimensions -- an agent can infer this is the tool for qualitative feedback on an image creative. However, there is no explicit when-to-use statement, no prerequisites, and no named alternative for adjacent tasks such as banner quality checks or fatigue checks.

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.