clippy

Update Clippy Item

update-item-tool

Edit the text of an existing item in a Clippy room, identified by its item id (the id field returned by store-item / list-items). Image bytes are immutable; this changes only the text.

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": {
      "room": "<room>",
      "item_id": "<item_id>",
      "text": "<text>"
    },
    "name": "update-item-tool"
  }
}

Input Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link).
`text`	Yes	The new text. For a text-only item this cannot be empty — delete it instead.
`item_id`	Yes	The item id (UUID) to edit, as returned in the `id` field of a stored/listed item.
`password`	No	Required only if the room is password-protected and you are not using owner_token.
`owner_token`	No	Optional. The room owner_token; bypasses the password on a locked room.

Output Schema

Name	Required	Description	Default
`code`	Yes	The room code containing the item.
`item`	Yes	The updated item.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that only text is editable, image bytes are immutable, and text cannot be empty for text-only items. This adds useful behavioral context beyond the schema.

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 well-structured sentences: first defines the action and identifier, second states the key constraint. No fluff, every sentence adds value.

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 5 parameters (100% schema coverage) and an output schema, the description covers the main purpose, key behavioral constraints, and parameter semantics adequately. No missing critical information for an agent to invoke the tool 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?

Schema coverage is 100%, and the description enriches each parameter: 'room' includes URL formats, 'text' adds constraint about emptiness, 'item_id' clarifies it's the UUID from store/list, and 'password'/'owner_token' give conditional usage rules. This adds significant meaning beyond 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?

The description clearly states 'Edit the text of an existing item' with a specific verb and resource, and distinguishes from siblings like delete-item-tool and store-item-tool by focusing on text editing and immutability of image bytes.

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?

The description explicitly says when to use (edit text), references item_id from store-item/list-items, and notes that image bytes are immutable. It does not explicitly list alternatives for deleting or storing items, but context from sibling tools and the name makes this clear.

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

All clippy tools Inspect

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

Need Help?