mcp-server

lock_marketplace_items

Destructive

MARKETPLACE items: lock — keep the chosen items unchanged by automatic sync (undo: unlock_marketplace_items). Use this when the user wants listings frozen. Needs confirm:true after the user agrees. Target item_ids or all_items:true.

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": {
      "marketplace_id": "<marketplace_id>"
    },
    "name": "lock_marketplace_items"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	true only after the user approved; without it the call returns confirm_required and nothing runs.
`item_ids`	No	itemId values (from list_marketplace_items) to act on. Use this OR all_items.
`all_items`	No	Apply to every item of the marketplace. Use this OR item_ids.
`project_id`	No
`marketplace_id`	Yes	integrationId of the marketplace (from list_marketplaces).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds useful behavior beyond annotations: the sync-freezing effect, the undo path, and the confirm gate; the schema supplies the confirm_required failure mode. It does not explain permissions or exactly why the operation is flagged destructive, but coverage is still strong.

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 definition is compact and front-loaded, starting with the resource and operation before stating the effect, undo path, and confirm requirement. The item_ids/all_items reminder slightly overlaps the schema, but it is short and helps with invocation.

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 mutation tool with annotations and no output schema, the description covers the key semantics: what locking does, the undo path, and the confirm requirement. It leaves project_id and permission/rate-limit details unaddressed, so it is not fully complete but is adequate for correct invocation.

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

Parameters3/5

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

Schema coverage is 80%, with confirm, item_ids, all_items, and marketplace_id already documented. The description reinforces confirm and target selection but adds little beyond the schema, and project_id remains undocumented in both the schema and the description.

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 states a specific verb ('lock') and resource ('MARKETPLACE items'), explains the effect ('keep the chosen items unchanged by automatic sync'), and names the undo sibling 'unlock_marketplace_items'. It is clearly distinguishable from the many other marketplace item operations.

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?

It gives explicit when-to-use guidance ('Use this when the user wants listings frozen'), names the undo alternative, and states the confirm:true requirement after user agreement. It also says whether to target item_ids or all_items.

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

All mcp-server 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?