creative-tagger-mcp

predict_creative

Compare creative tags with brand historical tag-level performance to produce a fit score and form a controlled-test hypothesis.

Instructions

Legacy-named observational pre-flight. Compare a creative's tags with the brand's historical tag-level performance; this is not a forecast or causal estimate. Use the fit score and tag associations to form a one-variable controlled-test hypothesis with predeclared success and stop criteria. Pass an analysis_id or raw attributes.

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": {
      "brand_name": "<brand_name>"
    },
    "name": "predict_creative"
  }
}

Input Schema

Name	Required	Description
`attributes`	No	Creative attributes, alternative to analysis_id, e.g. {hook_type, visual_format, cta, emotion, offer_type}
`brand_name`	Yes
`analysis_id`	No	Saved analysis id to score (from analyze_creative)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 16, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must fully disclose behavior. It clarifies the tool is observational and non-forecasting, implying read-only access. However, it does not explicitly state side effects, authentication needs, or output details beyond 'fit score and tag associations.' This is adequate but not thorough.

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?

The description is concise with three sentences, each serving a purpose: context, functionality, and usage. It is front-loaded and efficient, though could slightly expand on the missing brand_name without becoming overly long.

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 tool with 3 parameters, no output schema, and no annotations, the description is moderately complete. It explains the core action and usage pattern but omits output format details and the meaning of brand_name. This leaves the agent with unanswered questions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal value over the input schema: it restates the alternative between analysis_id and attributes and gives an example for attributes. However, the required brand_name parameter is completely unmentioned, and schema coverage is only 67%. The description fails to explain brand_name, leaving a significant gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Compare a creative's tags with the brand's historical tag-level performance.' It specifies that it is not a forecast or causal estimate, distinguishing it from prediction tools. It also explicitly mentions forming a hypothesis with predeclared criteria, setting it apart from sibling tools like analyze_creative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: it is a 'Legacy-named observational pre-flight' used to form controlled-test hypotheses. It instructs to 'Pass an analysis_id or raw attributes.' However, it does not explicitly state when not to use this tool or compare to alternatives like analyze_creative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server