google-cloud-console-mcp

List App Distribution releases

firebase_appdistribution_list_releases

List releases uploaded for a Firebase app using its app ID, ordered by creation time descending, with optional filters and pagination.

Instructions

Lists releases uploaded for a Firebase app, newest first by default.

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>"
    },
    "name": "firebase_appdistribution_list_releases"
  }
}

Input Schema

Name	Required	Description
`appId`	Yes	Firebase 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)
`filter`	No	AIP-160 filter, e.g. createTime >= "2024-01-01T00:00:00Z"
`pageSize`	No
`pageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses default ordering but nothing about pagination, permissions required, or result limits — significant gaps for a list tool with four parameters.

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 tight sentence with the ordering detail front-loaded and no filler. It is appropriately sized, though it is short relative to what the tool needs to explain.

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?

With no annotations, no output schema, and only half the parameters documented, the description should explain pagination and filtering behavior but does not. An agent cannot tell how to page through results or what a response contains.

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 50%: appId and filter are documented in the schema, but pageSize and pageToken have no descriptions anywhere. The description adds no parameter meaning beyond implying app scoping, so it fails to compensate for the coverage gap.

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?

States a specific verb (Lists) and resource (releases uploaded for a Firebase app), which is enough to separate it from get_release, upload_release, and delete_releases. It stops short of explicitly naming sibling tools or clarifying list-vs-get boundaries.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as firebase_appdistribution_get_release for a single release. The 'newest first by default' note hints at ordering but not at selection context.

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

Deploy Server