Skip to main content
Glama

Sortly MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Update an item or folder

sortly_update_item
Destructive

Change fields on an existing item or folder — e.g. set a new quantity after a stock count, rename it, or relocate a folder via parent_id. Only the fields you pass change; pass null to clear a nullable field. Sending tags or custom_attribute_values replaces them. WRITE. Sortly: PUT /api/v1/items/{item_id} (returns 204).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name.
tagsNoTag names, e.g. ["furniture", "used"].
notesNoFree-text notes.
priceNoUnit price.
item_idYesThe item's or folder's numeric id.
quantityNoHow many you have.
label_urlNoValue encoded in the primary QR code / barcode.
parent_idNoMove into this folder (null = root). To move PART of an item's stock use sortly_move_item.
photo_idsNoIds of photos already in the account to attach.
min_quantityNoMinimum level; a Quantity alert can fire when stock reaches it.
label_url_typeNoSymbology of the primary code.
label_url_extraNoValue encoded in the secondary code.
measured_quantityNoNew measured amount for a measured item.
label_url_extra_typeNoSymbology of the secondary code.
custom_attribute_valuesNoCustom field values. Look up ids with sortly_list_custom_fields first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations carry only destructiveHint=true, and the description shoulders the rest: partial-update semantics ('only the fields you pass change'), null-to-clear behavior, and that tags/custom_attribute_values are wholesale REPLACED. It also labels it WRITE, cites the PUT endpoint, and notes the 204 empty response – richly consistent with the destructive hint.

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?

Front-loaded with the core action and examples, then the critical replacement semantics, then a compact 'WRITE. PUT ... (returns 204).' trailer. No sentence is wasted and the most decision-relevant facts come first.

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?

For a 15-param mutation tool with 100% schema coverage and no output schema, the description covers the missing pieces an agent needs: replace-vs-merge behavior, null-clearing, and the no-content 204 return. Nothing essential to invoking it correctly is left unstated.

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 100%, so the 3 baseline applies, but the description adds real meaning the schema lacks: null clears nullable fields and tags/custom_attribute_values are replaced rather than merged. This clarifies mutation semantics for several of the 15 params beyond their one-line schema 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?

States a specific verb+resource ('Change fields on an existing item or folder') and immediately contrasts with the sibling operation (relocating via parent_id, with schema pointing to sortly_move_item). Concrete examples (stock count quantity, rename, relocate) let an agent distinguish it from sortly_create_item and sortly_move_item without opening a 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?

Offers clear contextual scenarios ('set a new quantity after a stock count, rename it, or relocate a folder') that signal when to reach for this tool, and the related move_item alternative is surfaced in the schema. It stops short of an explicit when-not statement in the description itself, so it is context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sortly MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources