Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__delete_edges

Delete multiple edges from a TigerGraph graph in one operation. Specify the edge type and a list of source and target vertex pairs to permanently remove relationships.

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. Dates show when Glama detected each change.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosing side effects. It warns that deletion is permanent and does not delete vertices, but does not mention behavior for missing edges, partial failures, or return values.

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, use cases, example, warning, and related tools. No redundant or irrelevant content is present.

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 covers purpose, usage, warnings, and an example, which is sufficient for a straightforward bulk delete operation. It does not specify return values or error semantics, but these are not critical given the tool's simplicity and the absence of an output schema.

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?

All parameters are described in the schema, and the description adds a concrete JSON example clarifying the expected edge objects with from_type, from_id, to_type, and to_id fields. This goes beyond the schema descriptions.

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 tool deletes multiple edges from a TigerGraph graph, with explicit use cases for bulk deletion. The verbs and resource scope are unambiguous.

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?

Provides explicit 'Use When' conditions, a warning that the operation is permanent and cannot be undone, and clarifies that vertices are not deleted. Related tools are also listed, helping the agent choose the correct operation.

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