Skip to main content
Glama
longbridge

longbridge

Official

Delete Watchlist Group

delete_watchlist_group
DestructiveIdempotent

Delete a watchlist group by numeric ID. Optionally purge its securities from all other groups.

Instructions

Delete a watchlist group by id (numeric). Set purge=true to also remove its securities from all other groups. Returns upstream API response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWatchlist group id
purgeYesWhether to also remove the securities from other groups

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe deleted watchlist group ID (echoed from the request).
deletedYesAlways `true` on success.
Behavior4/5

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

Annotations already indicate destructiveHint: true. The description adds context about the purge flag's effect and the return of the upstream API response, providing behavioral details beyond annotations.

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 concise sentences that are front-loaded with the primary action and provide essential details without any superfluous information.

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?

The description is adequate for a simple delete tool, covering the action, parameters, and return value. Given an output schema exists, it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds meaning by specifying 'numeric' for id and explaining the purge flag's purpose, enhancing understanding beyond the schema.

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 clearly states the action 'Delete' and the resource 'watchlist group by id', specifying the purge flag, which distinguishes it from sibling tools like create_watchlist_group and update_watchlist_group.

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?

The description implies usage for deleting a watchlist group and explains the purge parameter, but does not explicitly state when not to use or suggest alternatives. However, for a delete tool, the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server