Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__delete_edges

DestructiveIdempotent

Delete multiple edges (relationships) from a TigerGraph graph in one bulk operation. Removes specified connections permanently without deleting vertices.

Instructions

Delete multiple edges (relationships) from a TigerGraph graph.

Use When: • Removing multiple relationships • Bulk edge deletion • Graph restructuring

Quick Start:

{
  "edge_type": "FOLLOWS",
  "edges": [
    {"from_type": "Person", "from_id": "u1", "to_type": "Person", "to_id": "u2"},
    {"from_type": "Person", "from_id": "u2", "to_type": "Person", "to_id": "u3"}
  ]
}

Warning: • Operation is permanent and cannot be undone • Does not delete vertices

Related Tools: delete_edge, add_edges

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edgesYesList of edges with source and target vertex IDs.
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
edge_typeYesType of the edges.
graph_nameNoName of the graph. If not provided, uses default connection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false, but the description adds specifics: a warning that the operation is permanent and cannot be undone, and that it does not delete vertices. This clarifies the destructive scope beyond the generic annotation, adding value.

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 efficiently organized with a clear intro, 'Use When' bullet points, a compact JSON example, a warning section, and related tools. It is front-loaded with the purpose, avoids redundancy, and every section serves a practical function.

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 destructive bulk operation, the description covers usage conditions, provides a working example, warns about irreversibility and vertex behavior, and lists related tools. Parameter definitions are in the schema. Minor gaps like not elaborating on profile/graph_name usage (though schema covers them) or return behavior (no output schema) are acceptable here.

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?

While schema coverage is 100%, the schema's description for 'edges' is vague ('List of edges with source and target vertex IDs'). The Quick Start example explicitly shows nested fields (from_type, from_id, to_type, to_id), giving agents concrete understanding of the required structure. This meaningfully enhances parameter semantics 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 starts with a precise statement: 'Delete multiple edges (relationships) from a TigerGraph graph.' It specifies the verb (delete), resource (edges), and scope (multiple), clearly distinguishing from the sibling delete_edge (singular) without ambiguity.

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?

A dedicated 'Use When' section lists concrete scenarios (removing multiple relationships, bulk edge deletion, graph restructuring) and related tools (delete_edge, add_edges) are mentioned. However, it does not explicitly state when not to use (e.g., for a single edge) or give a comparative decision rule between delete_edges and delete_edge, so it falls short of a full 5.

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