Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Delete an integration connection

delete_integration_connection
Destructive

Deletes an integration connection from a workspace and removes related agent integration mappings, while preventing deletion of the default connection when other connections remain.

Instructions

Delete an integration connection from the workspace the credential resolves to, along with any agent integration mappings that use it. The default connection cannot be deleted while the integration has other connections. Only runs for a user signed in with OAuth; with an Orchestra API key it is refused.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "integration": "<integration>",
      "connection_id": "<connection_id>"
    },
    "name": "delete_integration_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationYes
connection_idYes
X-Orchestra-Account-IdNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.11.13-0
    • changedInput schema / properties / integration / enum
      Previous value: -[
      -  "AIRBYTE_CLOUD",
      -  "AIRBYTE_SERVER",
      -  "AIRFLOW",
      -  "ARCH",
      -  "ALTERYX_SERVER",
      -  "ANTHROPIC",
      -  "AWS_EC2",
      -  "AWS_ECS",
      -  "AWS_EMR",
      -  "AWS_EKS",
      -  "AWS_FIREHOSE",
      -  "AWS_GLUE",
      -  "AWS_LAMBDA",
      -  "AWS_RDS",
      -  "AWS_REDSHIFT",
      -  "AWS_S3",
      -  "AWS_BATCH",
      -  "AWS_BEDROCK",
      -  "AWS_SAGEMAKER",
      -  "AWS_SECRETS_MANAGER",
      -  "AWS_SES",
      -  "AWS_STEP_FUNCTIONS",
      -  "AZURE",
      -  "AZURE_CONTAINER_APPS",
      -  "AZURE_DATA_FACTORY",
      -  "AZURE_DATA_LAKE_STORAGE",
      -  "AZURE_KEY_VAULT",
      -  "AZURE_KUBERNETES_SERVICE",
      -  "AZURE_LOGIC_APPS",
      -  "AZURE_SYNAPSE_ANALYTICS",
      -  "AZURE_VM",
      -  "BAUPLAN",
      -  "BOOMI",
      -  "CDATA",
      -  "CENSUS",
      -  "CLICKHOUSE",
      -  "COALESCE",
      -  "COUNT",
      -  "DATADOG",
      -  "DATABRICKS",
      -  "DATAPROC",
      -  "DATAZEN",
      -  "DBT",
      -  "DBT_CORE",
      -  "DLT",
      -  "DOMO",
      -  "DREMIO",
      -  "DUCKDB",
      -  "EMAIL",
      -  "ESTUARY",
      -  "ETLEAP",
      -  "FABRIC",
      -  "FABRIC_SYNAPSE",
      -  "FIVETRAN",
      -  "FORTRA",
      -  "GCP_BIG_QUERY",
      -  "GCP_CLOUD_RUN",
      -  "GCP_CLOUD_FUNCTIONS",
      -  "GCP_CLOUD_STORAGE",
      -  "GCP_DATAFLOW",
      -  "GCP_DATAFORM",
      -  "GCP_DATASTREAM",
      -  "GCP_LOOKER",
      -  "GKE",
      -  "GITHUB_ACTIONS",
      -  "GOOGLE_CLOUD",
      -  "HEVO",
      -  "HEX",
      -  "HIGHTOUCH",
      -  "HTTP",
      -  "HUBSPOT",
      -  "INFORMATICA_IICS",
      -  "INFORMATICA_POWERCENTER",
      -  "KAFKA",
      -  "KEBOOLA",
      -  "KLEENE",
      -  "LIGHTDASH",
      -  "LINUX_SSH",
      -  "MARIADB",
      -  "MATILLION",
      -  "MATILLION_ETL",
      -  "METAPLANE",
      -  "MICROSOFT_TEAMS",
      -  "MICROSTRATEGY",
      -  "MONGODB",
      -  "MOTHERDUCK",
      -  "MYSQL",
      -  "N8N",
      -  "NIMBLE",
      -  "NOTION",
      -  "OMNI",
      -  "OPEN_AI",
      -  "ORCHESTRA",
      -  "PARADIME",
      -  "PAGER_DUTY",
      -  "PINECONE",
      -  "PORTABLE",
      -  "POSTGRES",
      -  "POWER_AUTOMATE",
      -  "POWER_BI",
      -  "PREFECT_CLOUD",
      -  "PYTHON",
      -  "QLIK",
      -  "QLIK_REPLICATE",
      -  "QUICKBOOKS",
      -  "RENDER",
      -  "RIVERY",
      -  "RUDDERSTACK",
      -  "SALESFORCE",
      -  "SAP",
      -  "SFTP",
      -  "SHAREPOINT",
      -  "SIGMA",
      -  "SISENSE",
      -  "SLACK",
      -  "SNOWFLAKE",
      -  "SNOWPLOW",
      -  "SODA",
      -  "SQL_MESH",
      -  "SQL_SERVER",
      -  "STITCH",
      -  "STREAMKAP",
      -  "TABLEAU_CLOUD",
      -  "TALEND_CLOUD",
      -  "THOUGHTSPOT",
      -  "TOBIKO_CLOUD",
      -  "TYPESAFE",
      -  "WEAVIATE",
      -  "WEBHOOK",
      -  "WELD",
      -  "WINDOWS_SSH"
      -]New value: +[
      +  "AIRBYTE_CLOUD",
      +  "AIRBYTE_SERVER",
      +  "AIRFLOW",
      +  "ARCH",
      +  "ASTRATO",
      +  "ALTERYX_SERVER",
      +  "ANTHROPIC",
      +  "AWS_EC2",
      +  "AWS_ECS",
      +  "AWS_EMR",
      +  "AWS_EKS",
      +  "AWS_FIREHOSE",
      +  "AWS_GLUE",
      +  "AWS_LAMBDA",
      +  "AWS_RDS",
      +  "AWS_REDSHIFT",
      +  "AWS_S3",
      +  "AWS_BATCH",
      +  "AWS_BEDROCK",
      +  "AWS_CLOUDWATCH_LOGS",
      +  "AWS_SAGEMAKER",
      +  "AWS_SECRETS_MANAGER",
      +  "AWS_SES",
      +  "AWS_STEP_FUNCTIONS",
      +  "AZURE",
      +  "AZURE_CONTAINER_APPS",
      +  "AZURE_DATA_FACTORY",
      +  "AZURE_DATA_LAKE_STORAGE",
      +  "AZURE_FUNCTIONS",
      +  "AZURE_KEY_VAULT",
      +  "AZURE_KUBERNETES_SERVICE",
      +  "AZURE_LOGIC_APPS",
      +  "AZURE_SYNAPSE_ANALYTICS",
      +  "AZURE_VM",
      +  "BAUPLAN",
      +  "BOOMI",
      +  "CDATA",
      +  "CENSUS",
      +  "CLICKHOUSE",
      +  "COALESCE",
      +  "COUNT",
      +  "DATADOG",
      +  "DATABRICKS",
      +  "DATAPROC",
      +  "DATAZEN",
      +  "DBT",
      +  "DBT_CORE",
      +  "DLT",
      +  "DOMO",
      +  "DREMIO",
      +  "DUCKDB",
      +  "EMAIL",
      +  "ESTUARY",
      +  "ETLEAP",
      +  "FABRIC",
      +  "FABRIC_SYNAPSE",
      +  "FIVETRAN",
      +  "FORTRA",
      +  "GCP_BIG_QUERY",
      +  "GCP_CLOUD_RUN",
      +  "GCP_CLOUD_FUNCTIONS",
      +  "GCP_CLOUD_STORAGE",
      +  "GCP_DATAFLOW",
      +  "GCP_DATAFORM",
      +  "GCP_DATASTREAM",
      +  "GCP_LOOKER",
      +  "GKE",
      +  "GOOGLE_CHAT",
      +  "GITHUB_ACTIONS",
      +  "GITLAB",
      +  "GOOGLE_CLOUD",
      +  "HEVO",
      +  "HEX",
      +  "HIGHTOUCH",
      +  "HTTP",
      +  "HUBSPOT",
      +  "INFORMATICA_IICS",
      +  "INFORMATICA_POWERCENTER",
      +  "KAFKA",
      +  "KEBOOLA",
      +  "KLEENE",
      +  "LIGHTDASH",
      +  "LINUX_SSH",
      +  "MARIADB",
      +  "MATILLION",
      +  "MATILLION_ETL",
      +  "METAPLANE",
      +  "MICROSOFT_TEAMS",
      +  "MICROSTRATEGY",
      +  "MONGODB",
      +  "MOTHERDUCK",
      +  "MYSQL",
      +  "N8N",
      +  "NIMBLE",
      +  "NOTION",
      +  "OMNI",
      +  "OPEN_AI",
      +  "ORCHESTRA",
      +  "PARADIME",
      +  "PAGER_DUTY",
      +  "PINECONE",
      +  "PORTABLE",
      +  "POSTGRES",
      +  "POWER_AUTOMATE",
      +  "POWER_BI",
      +  "PREFECT_CLOUD",
      +  "PYTHON",
      +  "QLIK",
      +  "QLIK_REPLICATE",
      +  "QUICKBOOKS",
      +  "RENDER",
      +  "RIVERY",
      +  "RUDDERSTACK",
      +  "SALESFORCE",
      +  "SAP",
      +  "SFTP",
      +  "SHAREPOINT",
      +  "SIGMA",
      +  "SISENSE",
      +  "SLACK",
      +  "SNOWFLAKE",
      +  "SNOWPLOW",
      +  "SODA",
      +  "SQL_MESH",
      +  "SQL_SERVER",
      +  "STITCH",
      +  "STREAMKAP",
      +  "TABLEAU_CLOUD",
      +  "TALEND_CLOUD",
      +  "THOUGHTSPOT",
      +  "TOBIKO_CLOUD",
      +  "TYPESAFE",
      +  "WEAVIATE",
      +  "WEBHOOK",
      +  "WELD",
      +  "WINDOWS_SSH"
      +]
  2. Addedv2026.10.12-0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only declare destructiveHint=true, while the description discloses the cascade (agent integration mappings using the connection are deleted too), the default-connection guard, and the authentication-mode restriction that causes refusal. That is exactly the kind of hidden consequence an agent needs before invoking a destructive tool.

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?

Three sentences, front-loaded with the action and its cascade, then the precondition, then the auth constraint. No filler and no repetition of the annotation-provided title.

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, cascading mutation this covers consequences, preconditions, and auth gates, which is most of what an agent needs; no output schema exists but the return value is not needed to decide. The only gap is that it never states whether the deletion is recoverable or what happens to the underlying credential.

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

Parameters3/5

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

With only 33% schema description coverage, the description carries some of the burden: it explains that the workspace is derived from the credential, which contextualizes the connection lookup. However it never explains what `integration` and `connection_id` select or how they combine, and the account-override header is documented only in 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?

States a specific verb+resource ('Delete an integration connection') and adds the scoping detail that it applies to the workspace the credential resolves to, plus the cascade to agent integration mappings. An agent can distinguish this from get/update/create_integration_connection without opening any schema.

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?

Gives two concrete preconditions: the default connection cannot be deleted while other connections exist, and the call only runs for a user signed in with OAuth (refused with an Orchestra API key). It does not point at alternatives such as update_integration_connection for non-destructive changes, but the when/when-not context is clearly present.

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