Skip to main content
Glama

Clean up a promo

clean_up_promo
DestructiveIdempotent

Deletes a promo's working files (scene clips, the joined file, sound tracks and stills) and keeps the finished videos: each size's final, or the latest draft when there is no final. Offer it when the person is done; get_promo's clean_up says how much it frees and what storage costs either way. After it, changing the promo renders every scene again. 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": {
      "promo_id": "<promo_id>"
    },
    "name": "clean_up_promo"
  }
}

Input Schema

NameRequiredDescriptionDefault
promo_idYesThe promo's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description still discloses the exact deletion scope, the retention rule, the re-render penalty, and that the operation is free. That is substantial context beyond what the structured fields carry.

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 tight sentences: what is destroyed first, then when to offer it and how to check cost, then the consequence. The fragment "Free." is terse but earns its place by pre-empting a cost question.

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 one-parameter destructive tool with full annotation coverage, the definition covers deletion scope, retention, cost, and aftermath, which is what an agent needs to act safely. Only the return value (e.g., space freed) is left unstated, and the description redirects that question to get_promo instead.

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?

Only one parameter, promo_id, with 100% schema description coverage, so the schema already explains it. The description adds nothing further about the identifier format or sourcing, which is acceptable at this coverage level but is baseline rather than additive.

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 verb (deletes) plus the exact resource set removed (scene clips, joined file, sound tracks, stills) and precisely what survives (each size's final, or the latest draft if no final). No sibling tool could be confused with this one.

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?

"Offer it when the person is done" gives the trigger condition, and the pointer to get_promo's clean_up field tells the agent how to check savings and storage cost before acting. The follow-on consequence (changing the promo after this re-renders every scene) effectively states when not to use it.

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