Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

create_creative

Create a new image creative by uploading a file to a media group using the media group ID and file attributes.

Instructions

Create a new image creative. The API uses multipart file upload — pass the media group ID and file attributes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCreative name
groupYesMedia group ID
descriptionNoCreative description
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions multipart file upload, which is useful, but it fails to specify required permissions, response format, or the meaning of 'file attributes', leaving ambiguity. The mention of 'file attributes' also appears inconsistent with the schema parameters.

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 sentences, front-loaded with the purpose. Somewhat concise, but the second sentence includes vague terminology ('file attributes') that reduces clarity; still appropriately short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with no output schema and no annotations, the description does not explain success/error outcomes or the multipart upload specifics. The schema omits the file attribute despite the description mentioning it, leaving significant gaps for an agent.

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?

Schema coverage is 100%, so baseline is 3, but the description adds little value beyond the schema. It refers to the 'group' parameter as media group ID (already in schema) and introduces 'file attributes' that are not in the schema, which confuses rather than clarifies.

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?

Clearly states 'Create a new image creative' with a specific verb and resource. Differentiates from sibling tools like update_creative and delete_creative, and from create_video_creative/create_rich_media_creative by specifying 'image'.

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?

Implies usage for creating image creatives but does not explicitly state when to use this tool vs alternatives. No exclusions or prerequisites mentioned; the multipart upload hint is technical, not guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adbutler/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server