Skip to main content
Glama

Copy timeline

copy_timeline

Copies a public timeline, or one of the user's own, to the user's account as a private timeline the user can edit. Copying is part of Time.Graphics Premium; without it, the tool returns an error with a link to the plans page.

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": {
      "timeline_id": "<timeline_id>"
    },
    "name": "copy_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
timeline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: copying is Premium-gated and returns an error pointing to the plans page when unavailable, which an agent cannot infer from readOnlyHint/destructiveHint/idempotentHint. It still doesn't say whether the copy is deep (events included) or what happens for inaccessible/nonexistent source timelines.

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?

Two tight sentences, front-loaded with the action and outcome, with the gating condition second. Nothing is redundant or padded.

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?

The mutation's safety profile is covered by annotations and the premium error path is disclosed, but with no output schema the description omits what is returned (e.g., the new timeline id) and leaves the optional title parameter unexplained. Adequate but with clear gaps for a two-parameter creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, yet the description never explains timeline_id (source identifier) or the optional title (whether it overrides the copied title). The phrase 'public timeline, or one of the user's own' hints at the id's meaning but does not compensate for the documentation gap.

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 and resource plus the source scope: copying a public timeline or one of the user's own into the user's account as a private, editable timeline. This clearly separates it from create_timeline and get_timeline without requiring the schemas.

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?

Gives clear selection context: the source must be public or owned by the user, and the result is private and editable. It does not explicitly contrast with create_timeline or say when a user should copy versus recreate, so exclusion guidance is only implied.

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