Skip to main content
Glama

Yuppsy

property_delete_story_item

Destructive

Delete a story item from an existing property.

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": {
      "storyId": "<storyId>"
    },
    "name": "property_delete_story_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyIdYesThe story item id that the website belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / storyId / description
      Added value: +"The story item id that the website belongs to."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is an irreversible-style write. The description adds only the 'existing property' existence constraint and says nothing about cascade effects (e.g., whether attached images/videos go with the item) or failure modes when the id is invalid.

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?

A single front-loaded sentence with no filler; the verb and resource come first. It is efficient but so terse that it leaves the prerequisites implicit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required id, full schema coverage, annotations present), so little prose is needed. However, the description claims property scoping while no property parameter exists, leaving unclear how the owning property is determined — a real gap for a destructive operation.

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?

With a single parameter at 100% schema description coverage, the schema already carries the semantics. The description adds no format, ownership, or scope detail for storyId, and the schema's own wording ('belongs to the website') is slightly at odds with the tool's 'property' framing, which the description does not reconcile.

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 uses a specific verb and resource ('Delete a story item') scoped to an existing property, which cleanly separates it from sibling creation tools like property_add_story_item. It does not explicitly name the media-specific delete siblings (property_delete_image/video), but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative for removing other item types. The phrase 'from an existing property' only faintly implies a prerequisite; nothing tells the agent how this differs from property_delete or the image/video delete tools.

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