Skip to main content
Glama
NigelThorne

Firebase MCP Server

by NigelThorne

list_collections

Retrieve top-level Firestore collections to inspect database structure and navigate document hierarchies in Firebase projects.

Instructions

List top-level collections in Firestore

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `handleListCollections` that executes `db.listCollections()` and maps the result to collection IDs.
    async function handleListCollections() {
      const collections = await db.listCollections();
      return collections.map((col) => col.id);
    }
  • src/index.ts:147-151 (registration)
    The registration of the `list_collections` tool in the `tools` array.
    {
      name: "list_collections",
      description: "List top-level collections in Firestore",
      inputSchema: { type: "object" as const, properties: {} },
    },
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. It fails to indicate return structure (array of collection IDs?), pagination behavior, or safety characteristics (read-only nature). Only basic scope is declared.

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?

Extremely efficient: 6 words convey exact operation, scope, and system. No redundancy, properly front-loaded with action verb.

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 zero-parameter tool but minimal given lack of annotations and output schema. Could benefit from noting return format or that results are limited to root collections only.

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?

Zero parameters present, establishing baseline 4 per rubric. No parameters require semantic explanation beyond 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?

Clear verb ('List') and resource ('top-level collections in Firestore'). The 'top-level' qualifier helps distinguish from sibling tool list_subcollections, though it does not explicitly differentiate from list_documents or query_collection.

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 guidance provided on when to use this versus siblings like list_subcollections (for nested collections) or list_documents. No mention of prerequisites like authentication or project selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NigelThorne/firebase_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server