Skip to main content
Glama

update_mcp_integration_capabilities

DestructiveIdempotent

Bulk enable or disable selected tools, prompts, and resources on an MCP integration; only specified capabilities change state, and toggles can be reversed.

Instructions

Bulk enable or disable capabilities (tools, prompts, resources) on an MCP integration. A reversible toggle, not a deletion: only the capabilities named in the array change state, the change hides or exposes them immediately for connected users, and re-running with enabled flipped restores them. Source the integration id from list_mcp_integrations and current capability names, types, and states from list_mcp_integration_capabilities. Returns a success confirmation message.

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": {
      "id": "<id>",
      "capabilities": "<capabilities>"
    },
    "name": "update_mcp_integration_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe MCP integration ID or slug
capabilitiesYesArray of capability updates

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1

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 by stating that only the capabilities named in the array change state, that effect on connected users is immediate, and that re-running with enabled flipped restores them. This actually explains why destructiveHint=true is set despite the operation being a reversible toggle rather than a deletion: it hides or exposes capabilities to live users. It also states the response is a success confirmation.

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 verb and resource, then the reversibility/impact model, then the sourcing workflow. Every sentence carries distinct information with no restatement of the tool name 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 simple two-parameter mutation with full schema coverage, an output schema, and annotations, this covers purpose, effect on users, reversibility, idempotency implications, and prerequisite lookups. The only minor omission is error behavior for unknown capability names, which is acceptable given the 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?

Schema coverage is 100%, so the baseline is 3; the description earns more by clarifying that 'enabled' is a target state applied per named capability and that array membership itself determines what is touched (capabilities omitted are untouched). It adds light meaning about where id and capability names come from, though it does not mention that id also accepts a slug as the schema does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb+resource: 'Bulk enable or disable capabilities (tools, prompts, resources) on an MCP integration.' The scope word 'bulk' and the enumerated capability types make the operation unambiguous. It does not explicitly distinguish itself from the sibling update_mcp_server_capabilities (the server-level analogue), leaving the integration-vs-server distinction to be inferred from the noun alone.

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 a concrete call sequence: source the integration id from list_mcp_integrations and the capability names, types, and states from list_mcp_integration_capabilities. That tells the agent what to read before writing. There is no explicit when-not guidance (e.g., prefer update_mcp_server_capabilities when targeting a server rather than an integration), so it stops short of full routing 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