Skip to main content
Glama

cinematic_ads_delete_template

DestructiveIdempotent

Delete one of the caller's saved Cinematic Ads templates. 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": {
      "template_id": "<template_id>"
    },
    "name": "cinematic_ads_delete_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesFrom cinematic_ads_list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered structurally. The description adds genuinely new context with the caller-scoped ownership ('one of the caller's saved') and the zero-cost note ('Free.'), but says nothing about irreversibility or post-delete state.

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?

Two short sentences, front-loaded with the action and resource; nothing is buried. The trailing 'Free.' is a terse fragment whose meaning (no credit cost) is inferable but not explicit.

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 delete whose annotations already convey destructive/idempotent semantics and which needs no output schema, the description is nearly sufficient. It could still state that the deletion cannot be undone, which is the main remaining gap.

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?

Single required parameter with 100% schema description coverage, which already tells the agent the UUID comes from cinematic_ads_list_templates. The description adds no format, sourcing, or constraint detail beyond the schema, so baseline 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 states a specific verb (Delete) and resource (one of the caller's saved Cinematic Ads templates), which is unambiguous and scopes ownership to the caller. It never names a sibling or explains how it relates to list_templates/get_template, but there is no competing delete tool, so confusion risk is low.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no warning that deletion is permanent or how to recover. The only routing hint ('From cinematic_ads_list_templates.') lives in the schema, not the description.

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