Skip to main content
Glama

Remove a still image

remove_still
DestructiveIdempotent

Removes a still image from a long-form project. Free. Returns how many stills are left.

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": {
      "project_id": "<project_id>",
      "still_id": "<still_id>"
    },
    "name": "remove_still"
  }
}

Input Schema

NameRequiredDescriptionDefault
still_idYesFrom add_still or get_project
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds two pieces of context the annotations cannot convey: the call is 'Free' and it returns a remaining-still count. It stops short of saying whether deletion is reversible or what happens to dependent sequences/renders.

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 short sentences with the action first, then cost, then return value; every clause carries information and nothing is padded.

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 two-parameter destructive tool with full annotation and schema coverage, the description covers cost and return shape, which the structured fields do not. The remaining gap is consequence disclosure — whether removal affects timelines, renders, or dependent assets — which matters for a destructive operation.

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?

Schema description coverage is 100% and both parameters document their provenance ('From add_still or get_project', 'From create_project'), so the schema does the heavy lifting. The description adds no further meaning about either identifier, which matches the baseline of 3.

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?

States a specific verb and resource ('Removes a still image') and scopes it to a 'long-form project', which tells an agent exactly what object is affected. It does not explicitly distinguish itself from the sibling remove_graphic, leaving media-type discrimination to the name alone.

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?

There is no when-to-use or when-not-to-use guidance, no mention of remove_graphic as the alternative for non-still media, and no prerequisites (e.g., whether the still must not be in use). The sentence describes the action rather than advising on selection.

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