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

google-cloud-console-mcp

by kutleloove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete App Distribution releases

firebase_appdistribution_delete_releases

Remove up to 100 Firebase App Distribution releases at once using their full resource names. Bulk-delete releases for a given app ID to clean up builds.

Instructions

Deletes up to 100 releases at once, by their full resource names.

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": {
      "appId": "<appId>",
      "releaseNames": "<releaseNames>"
    },
    "name": "firebase_appdistribution_delete_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesFirebase App ID (not the Android package name), format "1:1234567890:android:abcdef" — get it from firebase_list_android_apps / firebase_list_ios_apps (the `appId` field)
releaseNamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the 100-item batch cap, which is useful, but omits that deletion is destructive/irreversible, permission requirements, and how it behaves on invalid or unknown resource names. The safety profile of a destructive operation is left undocumented.

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?

A single sentence with no wasted words, and the batching scope and identifier semantics are front-loaded. It is tight, though arguably too terse given how much behavioral information is missing.

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

Completeness2/5

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

For a destructive, unannotated mutation tool with no output schema and only 50% parameter coverage, the description is thin. It never states irreversibility, required permissions, or the 101+ release edge case, leaving real gaps an agent would need before invoking it.

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?

Schema coverage is 50%: appId is well-documented in the schema (format and where to obtain it), so the description's main contribution is clarifying that releaseNames are 'full resource names' — a meaningful hint the bare array lacks. It does not, however, give the format/example of a release resource name. Baseline 3 for partial coverage is appropriate.

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 states a specific verb ('Deletes') and resource ('releases'), plus the batching scope ('up to 100 ... at once') and the identifier type ('full resource names'). This clearly separates it from reads like firebase_appdistribution_list_releases/get_release, though it does not explicitly contrast with other delete siblings such as firebase_appdistribution_delete_group.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g., required IAM roles), and no note on whether the deletion is reversible or what to do if more than 100 releases must be removed. The agent must infer the operating context entirely.

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