Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__delete_nodes

Delete multiple vertices from a TigerGraph graph by ID list or WHERE clause. Removes connected edges automatically; test with get_nodes or get_vertex_count before executing.

Instructions

Purpose: Delete multiple vertices (nodes) from the graph in a single operation.

When to Use:

  • Bulk deletion of vertices matching criteria

  • Delete specific set of vertices by IDs

  • Clear all vertices of a type

  • Data cleanup operations

Important Notes:

  • Warning: This operation is permanent and cannot be undone

  • Warning: Omitting WHERE will delete ALL vertices of the specified type

  • Connected edges will also be deleted (CASCADE behavior)

  • More efficient than multiple delete_node() calls

Usage Modes:

  1. By WHERE clause: delete_nodes(vertex_type='Person', where='age > 70')

  2. By ID list: delete_nodes(vertex_type='Person', vertex_ids=['id1', 'id2'])

  3. Delete all: delete_nodes(vertex_type='TempData') (no where/ids)

Safety Tips:

  • ALWAYS test WHERE clause with get_nodes() first

  • Use get_vertex_count() to verify expected deletion count

  • Consider backing up data before bulk deletions

Related Tools:

  • delete_node: Delete a single vertex

  • get_nodes: Preview vertices before deletion

  • get_vertex_count: Check deletion impact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whereNoFilter condition to select vertices to delete. Use TigerGraph WHERE syntax. Examples: - 'age > 70' - 'status == "inactive"' - 'created_date < "2020-01-01"' Warning: If omitted, ALL vertices of this type will be deleted!
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
graph_nameNoName of the graph (uses default if not specified)
vertex_idsNoOptional list of specific vertex IDs to delete (alternative to WHERE clause)
vertex_typeYesThe type of vertices to delete

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.2

TDQS

A5/5.0
Behavior5/5

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

The description openly discloses severe side effects: the operation is permanent and cannot be undone, omitting WHERE deletes ALL vertices of the specified type, and connected edges are deleted via CASCADE. These warnings are prominently placed in 'Important Notes' and 'Safety Tips', ensuring the agent understands the destructive and irreversible nature.

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?

The description is well-structured with clear sections (Purpose, When to Use, Important Notes, Usage Modes, Safety Tips, Related Tools) and is appropriately detailed for a destructive bulk operation. It is not verbose or redundant; every section adds value.

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

Completeness5/5

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

The description provides all necessary context: the operation's effect, when to use it, safety warnings, usage modes, and related tools. Even without an output schema, the agent knows what to expect (deletion, no return value implied) and how to proceed safely. The mention of efficiency relative to repeated delete_node calls further aids tool selection.

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

Parameters5/5

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

The input schema covers all five parameters with descriptions, and the tool description supplements them with concrete examples for 'where' (e.g., 'age > 70') and 'vertex_ids' (list of IDs). It also explains the behavior when parameters are omitted, such as the danger of removing 'where' and the default connection profile behavior.

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 purpose: 'Delete multiple vertices (nodes) from the graph in a single operation.' It also distinguishes this from the sibling tool delete_node (single vertex) and provides a 'When to Use' list that clarifies its scope, such as bulk deletion, clearing all vertices of a type, and data cleanup.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool versus alternatives, listing scenarios like bulk deletion, deleting by IDs, and clearing a type. It also references related tools: delete_node for single deletion, get_nodes for previewing, and get_vertex_count for checking impact, giving an agent clear decision guidance.

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/tigergraph/tigergraph-mcp'

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