Skip to main content
Glama

Ad Spec Guard

validate_creative_spec

Read-only

Check an image or video against a platform placement's required dimensions, aspect ratio, file size cap and accepted file types. Width and height are enough to answer whether a size fits a placement; supply file size and type as well when the file exists, and the result says which checks it could not perform. Returns each violation with its severity and the expected value.

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": {
      "platform": "<platform>",
      "format_key": "<format_key>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "validate_creative_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesPixel width of the file or of the planned creative.
heightYesPixel height of the file or of the planned creative.
platformYesAd platform. One of: google, linkedin, meta, microsoft, telegram, tiktok.
file_bytesNoFile size in bytes. Omit it when the file does not exist yet or its size is unknown; the weight check is then reported as not performed. Never estimate it.
format_keyYesPlacement format, for example 'feed_1x1' or 'story_9x16'. Call get_platform_specs with section 'image' for the list.
file_extensionNoFile type without the dot, for example 'jpg', 'png', 'mp4'. Omit it when unknown; the type check is then reported as not performed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds meaningful context beyond them: partial results are possible, the response reports which checks were skipped, and violations come back with severity and expected values. That return-shape disclosure is valuable given there is no output schema.

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?

Three sentences, front-loaded with the core purpose, followed by the sufficiency rule for required parameters and the return behavior. No redundant restatement of the name or title and no filler.

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

Completeness5/5

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

For a six-parameter, read-only validation tool with no output schema, the description covers what is checked, which inputs are sufficient versus optional, how omissions are reported, and the shape of violations. An agent has everything needed to call it correctly without further reading.

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%, so every parameter is already documented in the input schema, including the omission semantics for file_bytes and file_extension. The description reinforces the required-vs-optional framing ('width and height are enough') but adds no new format, unit, or constraint detail beyond what the schema states, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource: 'Check an image or video against a platform placement's required dimensions, aspect ratio, file size cap and accepted file types.' That is far more informative than the title or name alone. It does not explicitly contrast itself with get_platform_specs or validate_ad_copy, so an agent must infer the boundary between fetching specs and validating against them.

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?

It gives concrete conditional guidance: width and height are sufficient for a fit answer, and file size/type should be supplied only when the file actually exists. It stops short of naming alternatives or stating exclusions (e.g., when to prefer get_platform_specs first), so the guidance is clear but not exhaustive.

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.