Skip to main content
Glama

Export timeline image

export_image
Read-onlyIdempotent

Renders a timeline, the user's own or a public one, as a PNG image or a PDF file and returns a download link. Without Time.Graphics Premium, the file has a lower resolution, part of the events, and a Time.Graphics watermark, as on the website.

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": "export_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNopng
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?

Annotations already declare this is a safe, idempotent read, so the safety profile is covered. The description adds genuinely non-obvious behavior: without Premium the output is degraded in resolution, contains only part of the events, and carries a watermark. It does not mention link expiry, rendering time, or how Premium status is determined, which keeps it short of a 5.

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 compact sentences with the action and return value front-loaded, followed by the caveat about degraded output. Nothing is redundant with the title, and no sentence could be cut without losing information.

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 export tool with no output schema, the description covers what is produced (download link) and the main condition affecting output quality. Missing only secondary details such as link lifetime and whether the export is synchronous, which are minor for a read-only render.

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 0%, so the description carries the burden. It clarifies that timeline_id may refer to a public timeline, not just one the caller owns, and confirms the two format options. It never states the default format, ID format, or whether PDF differs in cost or fidelity, so the compensation is partial.

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 ('Renders a timeline') plus the output artifacts (PNG image, PDF file) and return shape (download link). This clearly separates it from data-returning siblings like get_timeline and list_my_timelines, which do not produce files.

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?

The phrase 'the user's own or a public one' implies the acceptable scope of timelines but gives no explicit when-to-use or when-not guidance versus get_timeline or copy_timeline. The agent can infer this is the export path, but must reason it out rather than being told.

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