Skip to main content
Glama

unpublish_service

DestructiveIdempotent

Seller withdraws a listing from discovery and prevents new orders. Existing orders and idempotent order replays remain available. Requires bearer authentication.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "unpublish_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance: existing orders and idempotent replays stay available, and bearer authentication is required. Those are non-obvious operational facts an agent could not get from the annotations alone. It stops short of saying whether the withdrawal is reversible or what a failed call looks like.

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?

Three short sentences, each carrying distinct information: the action, the carve-out for existing orders, and the auth prerequisite. The most important constraint is front-loaded and there is no 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?

For a single-parameter mutation whose annotations already cover safety profile, the description supplies the effect scope and auth requirement that matter most. It leaves out return behavior and error conditions, which is acceptable given no output schema but keeps it from being fully complete.

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 description coverage is 0%, so the description would need to compensate, but it says nothing about listing_id, its format, or its provenance. The parameter is a single self-describing identifier with a length bound, so the practical gap is small, but no meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Seller withdraws a listing from discovery") plus the concrete consequence ("prevents new orders"), which distinguishes it from read-side siblings like search_services. It never names publish_service as its inverse, so differentiation is implied by the tool name pairing rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the actor framing ("Seller withdraws a listing") and the effect on new orders, which helps an agent infer when it applies. There is no explicit when-not guidance or named alternative (e.g., cancel_order for existing orders), so an agent must infer the boundary itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources