Skip to main content
Glama

Edit item details

edit_item
DestructiveIdempotent

Correct an item in THIS user's library. new_title/new_creator save a personal override visible only to them; the shared catalog entry is untouched. fields sets any other detail the app's edit form allows, also as a personal override (book: title, author, summary, genres, cover_url; movie: title, director, cast_members, poster_url, backdrop_url, release_date, runtime_minutes, plot, genres; show: title, creator, cast_members, poster_url, backdrop_url, first_air_date, last_air_date, plot, genres, networks; album: title, artist, cover_url, release_date, total_tracks, duration_minutes, genres, label; anime: title, title_english, description, genres, studios, cover_url, banner_url; and the equivalents for podcasts, games and manga). Dates are YYYY-MM-DD, lists are arrays, images are https links, null puts a field back to the catalog's value. new_external_id relinks the item to a different catalog entry, which is the correct fix when the wrong film/show/album was added (re_enrich cannot fix a wrong match, it only refetches the same entry). Errors if no change field is supplied.

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

Input Schema

NameRequiredDescriptionDefault
titleNoCurrent title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
fieldsNoOther details to set for this user, by field name. Values: string, number, array of strings, or null to revert to the catalog value. An unknown field is an error that lists the editable ones.
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
new_titleNoNew title (if changing)
media_typeYesType of media
new_creatorNoNew author/artist/director/creator (if changing)
new_external_idNoNew external ID to re-link item

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. Changed5 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
      +  "additionalProperties": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": [
      +      "string",
      +      "number",
      +      "array",
      +      "null"
      +    ]
      +  },
      +  "description": "Other details to set for this user, by field name. Values: string, number, array of strings, or null to revert to the catalog value. An unknown field is an error that lists the editable ones.",
      +  "type": "object"
      +}
    • 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 / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • changedInput schema / properties / title / description
      Previous value: -"Current title (partial match supported)"New value: +"Current title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • changedInput schema / required
      Previous value: -[
      -  "media_type",
      -  "title"
      -]New value: +[
      +  "media_type"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses the semantics that matter for a destructiveHint=true, idempotentHint=true write: changes are personal overrides, the shared catalog record is untouched, and null reverts a field to the catalog value. What is missing is the response shape or confirmation of what the edit returns, but the override-versus-catalog model is exactly the context an agent needs before mutating.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences are tightly front-loaded with the override model and the re_enrich contrast. The middle sentence, however, is a single sprawling parenthetical field catalog that trails off into "the equivalents for podcasts, games and manga," which is padding that could live in the schema instead of the description.

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 7-parameter nested-object mutation with no output schema, the description covers what can be changed, the per-type constraints, the null-revert semantics, the relink path, and the error condition. The only real gap is that it never says what a successful call returns or how partial failures behave.

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 already 100%, so the baseline would be 3; the description earns more by enumerating the valid field names per media type (book, movie, show, album, anime, etc.) and by adding value conventions the schema omits: YYYY-MM-DD dates, arrays for lists, https links for images. It stays silent on item_id-versus-title addressing, but that is fully covered in the schema.

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?

"Correct an item in THIS user's library" gives a specific verb plus resource and scopes it to the user's own library, which separates it from catalog-level operations. It immediately clarifies that edits are personal overrides and that the shared catalog entry is untouched, a distinction no sibling name conveys.

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

Usage Guidelines5/5

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

The description routes between the tool's own modes (new_title/new_creator for title/creator, fields for everything else) and names an explicit alternative: new_external_id is "the correct fix when the wrong film/show/album was added," with the reason re_enrich cannot substitute. It also states the failure condition (errors if no change field is supplied), leaving little to inference.

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