google-cloud-console-mcp

Remove a project IAM role binding

gcp_remove_project_iam_binding

Revoke a single IAM role from a member on a GCP project while preserving all other bindings.

Instructions

Revokes one role from one member on a project, preserving all other bindings.

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": {
      "role": "<role>",
      "member": "<member>"
    },
    "name": "gcp_remove_project_iam_binding"
  }
}

Input Schema

Name	Required	Description
`role`	Yes
`member`	Yes
`projectId`	No	GCP project id; defaults to GOOGLE_CLOUD_PROJECT env var if omitted

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose a key trait: other bindings are preserved, so this is a surgical mutation rather than a policy overwrite. It stops short of noting permission requirements, idempotency/error behavior when the binding is absent, or whether it triggers IAM eventual consistency.

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?

A single tight sentence front-loads the action and the preservation guarantee. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a 3-param mutation with no annotations and no output schema, but the undocumented role/member formats and lack of prerequisite/permission notes leave real gaps for an agent to call it correctly.

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

Parameters2/5

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

Schema coverage is only 33%: role and member are bare strings with no format hints, and only projectId is documented (env-var default). The description mentions 'role' and 'member' conceptually but adds nothing on expected formats, e.g. 'user:email' vs 'serviceAccount:email' prefixes, which is exactly the gap the schema leaves.

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 (revokes), resource (role binding), and scope (one role from one member on a project). This clearly distinguishes it from the sibling gcp_add_project_iam_binding and from gcp_set_project_iam_policy, which replaces the whole policy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies it is the narrow, single-binding removal path versus the bulk set/add siblings, but it never names an alternative or states a when-to-use condition explicitly. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server