Skip to main content
Glama

Delete a posting slot

clipember_delete_posting_slot
DestructiveIdempotent

Remove one posting slot. Posts already scheduled at that time don't change.

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": {
      "slotId": "<slotId>"
    },
    "name": "clipember_delete_posting_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety profile is covered. The description adds one genuinely useful behavioral fact beyond them – that posts already scheduled at that time are not affected, i.e. deletion is not cascading – but says nothing about whether a repeat delete errors or is a silent no-op, nor about permission requirements.

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 short sentences, front-loaded with the action, and the second sentence is not filler – it conveys the non-cascading consequence. Nothing is wasted or buried.

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 destructive tool with annotations and no output schema, the description covers the essential action and its main side-effect boundary. Remaining gaps (behavior on missing/already-deleted IDs, where to obtain slotId) are modest but real.

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% and the single parameter slotId carries no prose description, so the description would need to compensate. It only implies the ID identifies the slot being removed; it does not say where the ID comes from, whether a non-existent or already-deleted ID is an error, or what format is expected.

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?

"Remove one posting slot" gives a specific verb (remove) and resource (posting slot) with an explicit scope of exactly one. It is clearly distinguishable from siblings like clipember_add_posting_slot or clipember_list_posting_slots by the verb alone, though no sibling is named.

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 only implied: an agent infers this is for deleting an existing slot, and the second sentence hints it is safe with respect to scheduled posts. There is no explicit when-to-use versus alternatives (e.g., cancel_scheduled_post, add_posting_slot) or any prerequisite such as needing the slot ID from list_posting_slots.

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