Skip to main content
Glama

update_mcp_integration_workspaces

DestructiveIdempotent

Grant or revoke workspace access to an MCP integration in bulk, optionally setting an organization-wide default and overriding existing per-workspace access.

Instructions

Grant or revoke workspace access to an MCP integration in bulk. Reversible: only the workspaces listed change, access applies or is removed immediately for all users in those workspaces, and re-running with enabled flipped undoes a change. Source the integration id from list_mcp_integrations, workspace ids from list_workspaces, and the current access state from list_mcp_integration_workspaces. 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>",
      "workspaces": "<workspaces>"
    },
    "name": "update_mcp_integration_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe MCP integration ID or slug
workspacesYesArray of workspace access updates; may be empty when only changing global_workspace_access
global_workspace_accessNoOrganisation-wide workspace access default
override_existing_workspace_accessNoWhen true, global_workspace_access replaces existing per-workspace settings

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.16.5
    • addedInput schema / properties / global_workspace_access
      Added value: +{
      +  "description": "Organisation-wide workspace access default",
      +  "properties": {
      +    "enabled": {
      +      "description": "Whether every workspace gets access by default",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "enabled"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / override_existing_workspace_access
      Added value: +{
      +  "description": "When true, global_workspace_access replaces existing per-workspace settings",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / workspaces / description
      Previous value: -"Array of workspace access updates"New value: +"Array of workspace access updates; may be empty when only changing global_workspace_access"
    • removedInput schema / properties / workspaces / minItems
      Removed value: -1
    • 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/5.0
Behavior4/5

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

Beyond the annotations (destructive, idempotent, non-read-only), the description discloses blast radius ('only the workspaces listed change'), immediacy and audience ('all users in those workspaces'), and reversibility ('re-running with enabled flipped undoes a change'). It does not mention permission or authorization requirements for this mutation, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the action and its reversibility, with no wasted filler. The closing line about returning a success confirmation is largely redundant given an output schema exists.

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 nested, four-parameter mutation tool with rich annotations and an output schema, the description covers scope, immediacy, reversibility, and id provenance well. Authorization requirements and the interaction between global_workspace_access and per-workspace overrides are left unaddressed.

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, but the description adds genuine value by specifying where the id and workspace ids should come from and by clarifying that flipping 'enabled' undoes a change. It says nothing about global_workspace_access or override_existing_workspace_access semantics, leaving those entirely to the schema.

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?

The description names a specific verb pair and resource ('Grant or revoke workspace access to an MCP integration') plus the bulk scope, which is more precise than the tool name alone. It does not distinguish itself from the near-namesake siblings update_integration_workspaces or update_mcp_server_user_access, so an agent must infer the difference.

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?

It gives concrete preconditions and an explicit sourcing workflow: integration id from list_mcp_integrations, workspace ids from list_workspaces, and current state from list_mcp_integration_workspaces. This is clear when/how guidance, but it offers no explicit exclusion telling the agent when a different update tool is the right choice instead.

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