mcp-server

unlock_marketplace_items

Destructive

MARKETPLACE items: release lock — clear the lock set by lock_marketplace_items so automatic sync updates the items again. Use this when frozen listings should sync again. 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": "unlock_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

A3.9/5.0

Behavior3/5

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

The description adds real consequence beyond the annotations: clearing the lock re-enables automatic sync updates. It also restates the confirm gate from the schema. But with destructiveHint=true and idempotentHint=false declared, it does not explain what is risked by unlocking (e.g. queued/overwritten changes) or why the call is non-idempotent.

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

Conciseness4/5

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

Front-loaded with the resource and action, then the effect, then the usage condition, then the parameters — a sensible ordering with no filler. The telegraphic dash/clause style is slightly clipped but nothing is wasted.

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 5-parameter mutation tool with annotations and no output schema, the description covers what to target, the confirm prerequisite, and the downstream effect. Gaps are minor: no coverage of project_id scoping and no note on partial failures across a batch.

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%, so the schema already documents confirm, item_ids, all_items and marketplace_id including the OR-exclusivity. The description repeats 'item_ids or all_items:true' and the confirm requirement without adding format or edge-case detail, and leaves project_id (undescribed in the schema) unexplained. Baseline 3.

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-plus-resource ('release lock' / 'clear the lock') scoped to marketplace items, and explicitly names the inverse operation lock_marketplace_items so the agent can place it in the lock/unlock pair 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?

'Use this when frozen listings should sync again' gives a concrete triggering condition and implicitly excludes the locking path. No explicit when-not guidance and it never mentions the sibling unlock_ad_items, but the MARKETPLACE prefix plus the named counterpart keep routing unambiguous.

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?