Skip to main content
Glama

Google Big Query

by com.googleapis.bigquery

list_table_ids

Read-onlyIdempotent

List table ids in a BigQuery dataset. Supports pagination. Use page_size to limit results and page_token to retrieve next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoOptional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.
datasetIdYesRequired. Dataset ID of the table request.
pageTokenNoOptional. Page token, returned by a previous call, to request the next page of results.
projectIdYesRequired. Project ID of the table request.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tablesNoThe tables that matched the request.
nextPageTokenNoA token that can be used to request the next results page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  2. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  4. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  5. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  6. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  7. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  8. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  9. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  10. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  11. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  12. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  13. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  14. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  15. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  16. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  17. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  18. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  19. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  20. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  21. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  22. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  23. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  24. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  25. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  26. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  27. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  28. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  29. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  30. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  31. Changed1 schema field changed
    • removedOutput schema / $defs / ListFormatTable / properties / type
      Removed value: -{
-  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
-  "readOnly": true,
-  "type": "string"
-}
  32. Changed1 schema field changed
    • addedOutput schema / $defs / ListFormatTable / properties / type
      Added value: +{
+  "description": "Output only. The type of table (e.g. TABLE, VIEW, EXTERNAL, MATERIALIZED_VIEW, SNAPSHOT).",
+  "readOnly": true,
+  "type": "string"
+}
  33. Changed3 schema fields changed
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
+  "type": "string"
+}
    • addedOutput schema / properties / nextPageToken
      Added value: +{
+  "description": "A token that can be used to request the next results page.",
+  "type": "string"
+}
  34. Changed3 schema fields changed
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
-  "format": "int32",
-  "type": "integer"
-}
    • removedInput schema / properties / pageToken
      Removed value: -{
-  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
-  "type": "string"
-}
    • removedOutput schema / properties / nextPageToken
      Removed value: -{
-  "description": "A token that can be used to request the next results page.",
-  "type": "string"
-}
  35. Changed3 schema fields changed
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
+  "type": "string"
+}
    • addedOutput schema / properties / nextPageToken
      Added value: +{
+  "description": "A token that can be used to request the next results page.",
+  "type": "string"
+}
  36. Changed3 schema fields changed
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
-  "format": "int32",
-  "type": "integer"
-}
    • removedInput schema / properties / pageToken
      Removed value: -{
-  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
-  "type": "string"
-}
    • removedOutput schema / properties / nextPageToken
      Removed value: -{
-  "description": "A token that can be used to request the next results page.",
-  "type": "string"
-}
  37. Changed3 schema fields changed
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
+  "type": "string"
+}
    • addedOutput schema / properties / nextPageToken
      Added value: +{
+  "description": "A token that can be used to request the next results page.",
+  "type": "string"
+}
  38. Changed3 schema fields changed
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
-  "format": "int32",
-  "type": "integer"
-}
    • removedInput schema / properties / pageToken
      Removed value: -{
-  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
-  "type": "string"
-}
    • removedOutput schema / properties / nextPageToken
      Removed value: -{
-  "description": "A token that can be used to request the next results page.",
-  "type": "string"
-}
  39. Changed3 schema fields changed
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Optional. Page token, returned by a previous call, to request the next page of results.",
+  "type": "string"
+}
    • addedOutput schema / properties / nextPageToken
      Added value: +{
+  "description": "A token that can be used to request the next results page.",
+  "type": "string"
+}
  40. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive nature of the tool. The description adds useful behavior beyond that by disclosing pagination support, which is not evident from the annotations.

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?

The description is short, front-loaded, and easy to parse. It loses a point because the pagination sentence contains wrong parameter casing, making it concise but not fully reliable.

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

Completeness4/5

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

Given the simple listing operation, full schema coverage, rich annotations, and an output schema, the description is mostly complete. The main gap is the parameter-name mismatch that could cause incorrect invocation if followed literally.

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 100%, so baseline is 3, but the description introduces misleading parameter names: it says use `page_size` and `page_token` while the schema defines `pageSize` and `pageToken`. An agent following the description could pass snake_case keys and fail. This actively undermines the schema rather than adding value.

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 'List table ids in a BigQuery dataset' uses a specific verb and resource, making the tool's purpose clear. It does not explicitly contrast with siblings like list_dataset_ids or get_table_info, but the resource scope is specific enough to avoid major confusion.

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 pagination guidance is present, but there is no explicit statement about when to choose this tool over siblings such as get_table_info or execute_sql_readonly. Usage context is implied rather than explicitly differentiated.

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

All Google Big Query toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct concern: full SQL execution, read-only SQL execution, and specific metadata lookups for datasets and tables. The two SQL tools overlap intentionally but are clearly separated by the read-only restriction and explicit guidance to prefer the read-only variant.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: execute_sql, get_dataset_info, list_table_ids. The readonly suffix on execute_sql_readonly is predictable and does not break the overall naming convention.

Tool Count5/5

Six tools is a well-scoped count for a BigQuery server: two query tools for read-only and full execution, plus four metadata discovery tools. Every tool serves a clear purpose without unnecessary bloat.

Completeness4/5

The set covers the core BigQuery workflows of running queries and discovering datasets/tables, with execute_sql capable of DDL, DML, and ML operations. Minor gaps exist around job management and project-level discovery, but these are not critical for most agent workflows.

Resources