Skip to main content
Glama

cinematic_ads_guide

Read-onlyIdempotent

Read this before any other cinematic_ads_* tool: the step-by-step guide for remaking an existing video ad with Cinematic Ads — what to ask the user, the order of the tools, the check that ends each step, the credit estimate to give and the one question to ask before paying, polling and errors. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cinematic_ads_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: the guide covers user prompts, tool order, end-of-step checks, credit estimates, a pre-payment question, and polling/error handling, plus the 'Free' cost signal that annotations do not express.

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?

Front-loads the imperative ordering directive, then enumerates the guide's contents in a single compact clause. The em-dash list is dense but every item (tool order, step checks, credit estimate, pre-payment question, polling, errors) is distinct information, with no filler.

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?

No output schema exists, but the description adequately previews what the guide delivers (sequence, checks, credit estimate, polling/error guidance) so the agent knows what it will get back. For a zero-parameter documentation tool this is essentially complete; only a hint at the guide's format/size is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on inputs.

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?

States a specific resource (a step-by-step guide for remaking an existing video ad with Cinematic Ads) and its positional role relative to every cinematic_ads_* sibling. An agent can immediately tell this is a documentation/orientation tool rather than an action tool.

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

Usage Guidelines5/5

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

Explicitly says 'Read this before any other cinematic_ads_* tool', giving a hard ordering constraint rather than a vague suggestion, and adds that it is free so there is no cost reason to skip it. Among 50+ siblings this routing instruction is exactly what is needed.

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