Skip to main content
Glama

Set dates

set_dates
DestructiveIdempotent

Set or clear the dates on one library item: started_at, finished_at, added_at. Each accepts YYYY-MM-DD, YYYY-MM, or YYYY (a year-only finish is kept as a year, not turned into January 1st), or "none" to clear. Use for imported histories that only carry years, and to fix a wrong date.

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": {
      "media_type": "<media_type>"
    },
    "name": "set_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoExact title of the item (or pass item_id)
item_idNoLibrary item id (UUID), as shown by get_details. Preferred over title.
added_atNoWhen the item entered the library: YYYY-MM-DD, YYYY-MM, or YYYY. Use when importing from another app that recorded it.
media_typeYesType of media
started_atNoYYYY-MM-DD, YYYY-MM, YYYY, or "none" to clear. For albums this is the first listen.
finished_atNoYYYY-MM-DD, YYYY-MM, YYYY, or "none" to clear. For albums this is the last listen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value by explaining that passing "none" clears a date and that a year-only finish is preserved rather than normalized to January 1st. It does not say whether omitting a field leaves that date untouched or clears it, nor what happens if the item or media_type doesn't match — the main open behavioral question for a setter.

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: the first front-loads scope and the accepted formats, the second front-loads the use cases. No filler and no repetition of the tool title.

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 destructive, idempotent mutation with no output schema, the definition covers formats, clearing, and the year-only edge case well. The one meaningful omission is partial-update semantics: whether fields left out of the call are preserved or reset, which matters given destructiveHint=true.

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%, so the baseline is 3. The description does add one genuinely new semantic — year-only values are kept as years rather than coerced to January 1st — but the rest of the format guidance (accepted shapes, "none" to clear) is already present in the property descriptions.

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?

The description opens with a precise verb+resource pair ('Set or clear the dates on one library item') and enumerates exactly which fields are affected (started_at, finished_at, added_at). That field-level scope is enough to separate it from neighboring setters like set_progress or set_rating without opening the schema.

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?

It gives concrete when-to-use cases: imported histories that only carry years, and correcting a wrong date. It does not state when not to use it or name an alternative tool, but the positive guidance is specific enough to route an agent correctly.

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