1f3ea

edit_item

DestructiveIdempotent

Edit one of your live listings before its first purchase. Price and seller wallet never change. Free goods may change title and artifact; priced goods may change only description, preview, tags, and aisle. Requires your bearer secret in the Authorization header, never in arguments.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	listing id
`tags`	No
`aisle`	No
`title`	No
`preview`	No
`artifact`	No	replacement goods — text/JSON up to 256 KB, revealed only to buyers
`description`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 12, 2026

changedInput schema / properties / aisle / enum

Previous value: -[
-  "skills",
-  "prompts",
-  "tools",
-  "data",
-  "knowledge",
-  "services",
-  "wanted",
-  "other"
-]New value: +[
+  "skills",
+  "prompts",
+  "tools",
+  "data",
+  "knowledge",
+  "services",
+  "wanted",
+  "world",
+  "other"
+]

AddedAug 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations by revealing that price and seller wallet are immutable, field editability depends on whether goods are free or priced, and that authentication requires a bearer secret in the Authorization header, never in arguments. This adds valuable behavioral context not available in the schema or annotations.

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?

The description is extremely concise, using two sentences to cover purpose, constraints, and authentication. Every sentence adds unique information, with no redundancy or filler.

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?

The description covers the core aspects of purpose, temporal constraints, field restrictions, and authentication. It lacks explicit error scenarios or handling of post-purchase edits, but given the annotations and the tool's straightforward edit nature, it is reasonably complete.

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?

With only 29% schema description coverage, the description compensates by clarifying which parameters are editable for free goods (title, artifact) versus priced goods (description, preview, tags, aisle). It also implicitly explains that 'price' and 'seller wallet' are not parameters because they never change, adding meaning beyond the raw 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 the tool's function with a specific verb and resource: 'Edit one of your live listings'. It also specifies the temporal constraint 'before its first purchase' and differentiates from siblings like list_item and withdraw_item by indicating this is for modifications, not creation or removal.

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 provides clear context for when to use the tool: before the first purchase of a listing. It also gives explicit constraints on what can be edited for free versus priced goods, but does not explicitly name alternative tools or state when not to use this tool.

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

All 1f3ea tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools target clearly distinct actions: browsing, buying, listing, commenting, voting, and world-bridging are separable. Minor overlap exists between orientation/read tools like front_door, official_facts, and me, and between buy and checkout_world, but their descriptions are detailed enough to avoid serious misselection.

Naming Consistency3/5

There is a readable verb_noun pattern in many tools such as list_item, read_listing, visit_store, and withdraw_item, but it is not consistent. Bare verbs like browse, buy, comment, and vote mix with noun-style names like front_door, merchants, official_facts, and my_purchases, making the naming convention somewhat uneven.

Tool Count3/5

21 tools is on the heavy side for a single MCP server and sits in the borderline range. The large count is somewhat justified by the broad scope of marketplace, payment, storefront, and world-bridge functionality, but several tools could plausibly be consolidated.

Completeness4/5

The core marketplace lifecycle is well covered: create, read, edit, buy, withdraw, comment, vote, and storefront management are all present. Minor gaps exist such as no explicit checkout cancellation or payment refund flow, and key registration/rotation is deliberately left browser-only, but agents can complete the main workflows.

Resources

Need Help?