Skip to main content
Glama

cinematic_ads_list_projects

Read-onlyIdempotent

List the caller's Cinematic Ads projects (newest first) and the workspaces whose credits they can spend (id, name, role) — pass a workspace id to cinematic_ads_create_project to have that workspace pay. Free. Call cinematic_ads_guide first. Cinematic Ads is open to every Wandura account; everything is paid from the project's wallet — the user's own credits for a personal project (paid steps need a paid Wandura plan), the workspace's credits for a workspace project. Cinematic Ads remakes an existing video ad for the user's own app or brand: same shots, timing and style, new people, product, language and brand. Flow (the web studio's steps): cinematic_ads_create_project with original_ad_url → cinematic_ads_analyze → poll cinematic_ads_get_project until project.status is 'ready' → optionally cinematic_ads_update_project (brand kit, language, video model), cinematic_ads_brand_scan, cinematic_ads_refine + cinematic_ads_update_asset → cinematic_ads_make_images → cinematic_ads_make_video → poll until production.done is true → cinematic_ads_export → poll until exports[0].status is 'done' and use exports[0].url.

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_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description only needed to add context — and it does: newest-first ordering, the exact fields returned per workspace, and the fact that this call costs nothing while downstream production steps draw on a project or workspace wallet.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose, cost and prerequisite are front-loaded, but roughly two-thirds of the text is a product pitch and an eleven-step cross-tool workflow that duplicates cinematic_ads_guide and does not help an agent call this zero-argument list tool. That tail does not earn its place in this definition.

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 no-parameter, read-only list tool with no output schema, the description covers what is returned (projects, plus workspace id/name/role), the ordering, the cost, and the prerequisite. Only the individual project fields are left unspecified, which is a minor gap.

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 no parameter semantics to document and the baseline is 4. The description correctly adds no pseudo-parameter guidance.

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 opening clause states a specific verb+resource and even the ordering and returned fields: 'List the caller's Cinematic Ads projects (newest first) and the workspaces whose credits they can spend (id, name, role)'. That is unambiguous and clearly distinct from cinematic_ads_list_templates or browse_library.

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 actionable routing guidance ('pass a workspace id to cinematic_ads_create_project to have that workspace pay'), a cost signal ('Free'), and a prerequisite ('Call cinematic_ads_guide first'). It stops short of stating when NOT to use this tool, but the context it provides is genuinely operational.

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