Skip to main content
Glama
Sign In
google-cloud-console-mcp

google-cloud-console-mcp

by kutleloove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove testers from a group

firebase_appdistribution_remove_testers_from_group

Remove testers from a Firebase App Distribution group, revoking their access to releases shared with that group.

Instructions

Removes tester emails from a group (they lose access to releases shared with that group).

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": {
      "groupName": "<groupName>",
      "emails": "<emails>"
    },
    "name": "firebase_appdistribution_remove_testers_from_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYes
groupNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose the consequence of removal (loss of access to group-shared releases), which is useful behavioral context for a mutation tool. However it omits whether emails must exist, error behavior for unknown emails, and reversibility beyond 're-add'.

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 economical sentence with the core action front-loaded and the consequence appended. 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?

No annotations, no output schema, and 0% schema description coverage because this is a mutation tool. The description covers the essential consequence but leaves parameter semantics and edge-case behavior unaddressed – the minimum for correctness but with clear gaps.

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 0% – both parameters (groupName, emails) are undocumented in both schema and description. The description mentions 'tester emails' and 'group' generically, at least mapping 'emails' to the array and 'groupName' to the group, but no format, limits, or semantics are given.

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: removing tester emails from a group. Clearly distinguishes it from the sibling firebase_appdistribution_remove_testers (flat removal) and firebase_appdistribution_add_testers_to_group (inverse).

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 consequence clause ('they lose access to releases shared with that group') implies when this is appropriate, but no explicit when/when-not guidance or alternative routing is given. Adequate minimum viability only.

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