Skip to main content
Glama

timeline_manage

Manage timeline housekeeping by renaming, duplicating, deleting, or converting the current timeline into a media pool item.

Instructions

Timeline housekeeping. action: 'rename' (timeline name or current → new_name), 'duplicate' (→ new_name), 'delete' (timeline name; irreversible), 'compound_to_media' (get media pool item of current timeline).

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": {
      "action": "<action>"
    },
    "name": "timeline_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
actionYes
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose one genuinely important trait — that 'delete' is irreversible — and clarifies that 'compound_to_media' returns the media pool item of the current timeline. It says nothing about what duplicate produces (a new timeline object? a bin item?), whether rename affects references elsewhere, or what a successful call returns for each action.

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?

A single front-loaded sentence plus a compact action list; every clause carries information and there is no filler. The arrow shorthand ('→ new_name') is slightly terse but still parseable in context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-in-one mutation tool with no annotations and no output schema, the definition covers the action vocabulary and the destructive nature of delete, which is the critical piece. It is incomplete on return values and post-condition behavior for duplicate and compound_to_media, which an agent would need to chain calls correctly.

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?

Schema coverage is 0% and 'action' has no enum in the schema, so the description is the only source of valid action values — a substantial contribution. It also maps parameters to actions (name vs. new_name, and that name defaults to the current timeline for rename), which the bare schema does not convey. Remaining ambiguity: how an omitted 'name' resolves for delete or duplicate is unstated.

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 names a specific resource (timeline) and enumerates four concrete operations: rename, duplicate, delete, compound_to_media. 'Housekeeping' alone would be vague, but the action list disambiguates it from siblings like timeline_create, timeline_get, and timeline_settings. It does not explicitly state the boundary against those siblings, keeping it below a 5.

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

Usage Guidelines3/5

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

Usage is implied through the per-action semantics rather than stated: the agent can infer that 'delete' is for removal and 'duplicate' for copying. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. use timeline_create for a brand-new empty timeline). The parenthetical 'irreversible' on delete is the only routing-adjacent warning.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.