Skip to main content
Glama

Plan a short ad

plan_short
Read-only

Before writing a script for a short vertical ad: the timeline for a clip of video_seconds, with a word budget, where the hook, value and call to action go, and the held end card. With script, also says whether it fits. Free.

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": {
      "video_seconds": "<video_seconds>"
    },
    "name": "plan_short"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptNo
video_secondsYesThe generated clip's length, e.g. 5 or 10
end_card_secondsNo0 for no end card (not recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a planning tool, and the description adds value beyond it: the tool is free, it derives a word budget, it fixes where the hook/value/CTA sit and that the end card is held, and passing a script triggers a fit check. Return shape is described conceptually, though pagination/format details are not applicable here.

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?

One front-loaded sentence with no filler; the precondition leads and outputs follow. The phrasing is telegraphic ('the timeline for a clip of video_seconds', bare 'Free.') and reads slightly clipped, but nothing is wasteful.

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?

For a read-only three-parameter planning tool with no output schema, the description covers the inputs, the returns, and the cost model. The main residual gap is the exact form/units of the emitted word budget and timeline, which an agent must discover from the response.

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

Parameters4/5

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

Schema coverage is 67%, and the description compensates by tying video_seconds to the timeline/word budget and explaining what the optional script parameter unlocks (a fit determination). The held end card ties to end_card_seconds. It does not restate the 0-6 second bounds or the 0-disables-end-card rule, leaving that to the schema.

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 names a concrete resource: a timeline plan for a vertical short ad, covering word budget, beat placement (hook/value/CTA) and the held end card. That distinguishes it from the mutation/render siblings. The verb is only implied ('Before writing a script...') rather than stated outright, which keeps it from 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 Guidelines4/5

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

It gives a clear usage window: call this before writing a script for a short vertical ad, and it notes the conditional behavior when a script is supplied (returns a fit verdict). It does not state when not to use it or name an alternative planning path, so it stops short of full routing guidance.

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.

Resources