Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__delete_nodes

DestructiveIdempotent

Delete multiple graph vertices in one operation using filters, ID lists, or entire vertex types. Removes connected edges permanently (cascade); verify with get_nodes or get_vertex_count first.

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.

  1. First observedv1.0.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes further by warning that deletion is permanent and cannot be undone, that omitting WHERE deletes ALL vertices of the type, and that connected edges are deleted via CASCADE. These are critical behavioral details that an agent needs to know before invoking a destructive operation. It adds context beyond the annotations without contradiction.

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-organized with clear sections: Purpose, When to Use, Important Notes, Usage Modes, Safety Tips, and Related Tools. It front-loads the purpose and critical warnings (permanence, cascade) before diving into modes. Each sentence contributes actionable information, and the structure makes it easy to scan. No redundancy or filler.

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?

For a destructive bulk operation, the description is complete. It covers all usage modes, safety precautions, the cascade behavior, and references related tools for preview and verification. It even includes examples for WHERE clauses. There is no output schema, but that is not necessary for a deletion tool. An agent has everything needed to invoke it correctly and safely.

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 description coverage is 100%, so parameters are already well-documented. The description adds value by explaining usage modes (by WHERE, by ID list, delete all) and providing concrete examples of WHERE syntax (e.g., 'age > 70'). It also clarifies the relationship between where and vertex_ids as alternatives, which is not fully explicit in the schema. This goes beyond the schema baseline of 3.

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 purpose is explicitly stated as 'Delete multiple vertices (nodes) from the graph in a single operation.' It clearly identifies the verb (delete), resource (vertices/nodes), and scope (multiple, single operation). It also distinguishes itself from the sibling delete_node by noting it handles bulk deletion and is more efficient, making it easy for an agent to select the right tool.

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 'When to Use' section lists specific scenarios: bulk deletion, deletion by IDs, clearing all vertices of a type, and data cleanup. It also explicitly names alternatives (delete_node for single vertex, get_nodes for preview, get_vertex_count for impact) and provides safety tips like testing with get_nodes first. This gives clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools