Skip to main content
Glama

Set progress

set_progress
DestructiveIdempotent

Update how far the user is through an in-progress item. Books: current page, the page count of their copy, and/or a reading percentage (for audiobooks and e-readers). Shows: current season + episode. Anime: episodes watched. Manga: chapter and/or volume read up to. Comics: an issue read (issue), or every issue up to it (issue + through), on a day (read_on, default today).

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_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueNoIssue number read, as printed: "12", "½", "Annual 1" (comics only)
titleNoTitle of the item (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
volumeNoLast volume read (manga only)
chapterNoLast chapter read (manga only)
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
read_onNoComics only: the day the issue was read, YYYY-MM-DD (default today)
throughNoComics only: mark every issue up to and including `issue` read (issues already read keep their day)
media_typeYesType of media (progress only applies to books, shows, anime, manga and comics)
page_countNoPages in the copy they are reading (books only); null clears it
current_pageNoCurrent page number (books only)
current_seasonNoCurrent season number (shows only)
current_episodeNoCurrent episode number within the season (shows only)
episodes_watchedNoTotal episodes watched so far (anime only)
reading_progressNoPercent read, 0 to 100 (books only, for formats without pages); null clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / issue
      Added value: +{
      +  "description": "Issue number read, as printed: \"12\", \"½\", \"Annual 1\" (comics only)",
      +  "type": "string"
      +}
    • changedInput schema / properties / media_type / description
      Previous value: -"Type of media (progress only applies to books, shows, anime and manga)"New value: +"Type of media (progress only applies to books, shows, anime, manga and comics)"
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "show",
      -  "anime",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "show",
      +  "anime",
      +  "manga",
      +  "comic"
      +]
    • addedInput schema / properties / read_on
      Added value: +{
      +  "description": "Comics only: the day the issue was read, YYYY-MM-DD (default today)",
      +  "type": "string"
      +}
    • addedInput schema / properties / through
      Added value: +{
      +  "description": "Comics only: mark every issue up to and including `issue` read (issues already read keep their day)",
      +  "type": "boolean"
      +}
  2. Changed9 schema fields changed
    • addedInput schema / properties / chapter
      Added value: +{
      +  "description": "Last chapter read (manga only)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / item_id
      Added value: +{
      +  "description": "Library item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.",
      +  "type": "string"
      +}
    • changedInput schema / properties / media_type / description
      Previous value: -"Type of media (progress only applies to books, shows, and anime)"New value: +"Type of media (progress only applies to books, shows, anime and manga)"
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "show",
      +  "anime",
      +  "manga"
      +]
    • addedInput schema / properties / page_count
      Added value: +{
      +  "description": "Pages in the copy they are reading (books only); null clears it",
      +  "minimum": 0,
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / reading_progress
      Added value: +{
      +  "description": "Percent read, 0 to 100 (books only, for formats without pages); null clears it",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / title / description
      Previous value: -"Title of the item (partial match supported)"New value: +"Title of the item (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • addedInput schema / properties / volume
      Added value: +{
      +  "description": "Last volume read (manga only)",
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "media_type",
      -  "title"
      -]New value: +[
      +  "media_type"
      +]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

While annotations confirm this is a destructive operation, the description adds crucial behavioral nuances. It specifies differences in progress representation, such as how books can use page count, specific pages, or a percentage for audiobooks/e-readers, adding important context beyond the basic 'update' behavior.

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?

The description is dense, but it is highly efficient. It front-loads the core purpose and then uses a structured breakdown (e.g., 'Books:', 'Shows:', 'Anime:') to map all the complex parameters efficiently without unnecessary filler.

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

Completeness5/5

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

Given the complexity of tracking progress across five diverse media types, the definition is highly complete. It defines the specific progress metrics (e.g., `current_season + episode` vs. `episodes_watched`) and provides the necessary domain-specific logic to use the 14 parameters correctly.

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

Parameters5/5

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

The schema is complex, and the description compensates perfectly by detailing real-world constraints and required formats. For instance, it explains that comics issues can be represented as '½' or 'Annual 1,' and clarifies that `read_on` is specifically for comics, adding indispensable meaning that goes far beyond the technical schema type definitions.

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 clearly states the tool's purpose is to 'Update how far the user is through an in-progress item.' It excels by distinguishing its function across five different media types (Books, Shows, Anime, Manga, Comics), making its scope specific and easy to identify as distinct from simple status changes.

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?

The description contains no guidance on when to use this tool versus similar mutation tools in the sibling set (e.g., set_rating, update_status, or set_formato). It only focuses on the mechanics of progress tracking, leaving the agent to rely entirely on the tool name and schema to differentiate it from other state modifiers.

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