source_delete
Permanently remove a workspace source or destination endpoint after dependency checks. The client must obtain confirmation and pass confirm=true.
When to use it
Use source_delete to delete a source endpoint. This tool operates at workspace scope. It does not require a project context unless a filtering argument explicitly asks for one.
Plugin requirements
Connector dependency depends on the endpoint. These tools manage endpoint configuration, policies or grants; they do not install a connector or add capabilities to it. A plugin-backed endpoint must reference a configured connector installation. Use the plugin setup guides for configuration. Inspect the workspace’s plugin installations and check the installation before executing it.
Arguments
| Name | Type | Required | Default | Constraints |
|---|---|---|---|---|
id | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
confirm | boolean | Yes | — | Must equal true |
idempotencyKey | string | Yes | — | Minimum length: 8; Maximum length: 200 |
View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.
Response shape
The implementation constructs payloads using these fields: deleted, sourceId. The returned fields depend on the execution path.
MCP returns a text block containing the JSON operation result and a
structuredContent copy. The envelope includes data, completeness,
truncated, freshness, and warnings. Depending on the operation it can also
include nextCursor, evidence, job, or receipt.
Check those fields before treating a conversational summary as the result.
When a job is returned, inspect its status with the appropriate execution tool;
a queued response is not confirmation that work finished. Follow evidence links
when checking the underlying records.
Input methods
This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.
Open Data Endpoints in the workspace and select the endpoint you intend to inspect or manage. Read its name, direction, capability and target before changing it. Use the endpoint’s edit/delete workflow for changes; review its consumers and any confirmation before committing.
Use Semogram’s source_delete tool to delete a source endpoint. Inspect the required inputs and target first, then show me what will change before executing it.
Use real resource IDs returned by earlier reads; a resource name is not a UUID. Do not fill missing business inputs with invented values.
Use a workspace API key with endpoints:write. Set SEMOGRAM_API_KEY in your shell; replace resource placeholders with real IDs. This is an HTTP resource request, not an MCP JSON-RPC message.
curl --request DELETE "https://platform.semogram.com/api/v1/data-endpoints/<ID_UUID>" \
--header "Authorization: Bearer ${SEMOGRAM_API_KEY}"This is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "source_delete",
"arguments": {
"id": "<ID_UUID>",
"confirm": true,
"idempotencyKey": "<UNIQUE_KEY_FOR_THIS_OPERATION>"
}
}
}FAQ
What access and approvals are required?
Required permission scopes: endpoints:write.
OAuth uses current workspace membership; API keys use their assigned scopes
and grants. Discovery can exclude tools the caller cannot use.
Read-only annotation: No. Destructive annotation: Yes.
The schema requires confirm: true. Ask the user to review the exact target and approve the operation before calling it.
How should I handle retries?
The server marks this operation as idempotent. When an idempotencyKey is accepted, keep the same key only for a retry of the exact same input; use a new key for new work. For 429 responses, honor Retry-After rather than retrying immediately.
Why is this tool missing or returning an error?
Confirm the workspace, resource IDs, and permission scopes. Read the returned error before changing the request. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.