Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-dashboards

Lists dashboards with pagination and service filtering. Supports fields selection and cursor-based navigation.

Instructions

List dashboards with pagination and service filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include (e.g. 'owners,tags,followers,charts')
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
serviceNoFilter by service FQN
includeNoInclude deleted entitiesnon-deleted
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • The actual handler function for list-dashboards — makes a GET request to /dashboards with the provided params (pagination, service filter, etc.).
    export async function listDashboards(params: z.infer<typeof listDashboardsSchema>) {
      return omClient.get("/dashboards", params);
  • Zod schema defining input parameters for list-dashboards: fields, limit (default 10), pagination cursors (before/after), service filter, include mode, and extractFields.
    export const listDashboardsSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include (e.g. 'owners,tags,followers,charts')"),
      limit: z.coerce.number().optional().default(10).describe("Number of results per page"),
      before: z.string().optional().describe("Cursor for backward pagination"),
      after: z.string().optional().describe("Cursor for forward pagination"),
      service: z.string().optional().describe("Filter by service FQN"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
      extractFields: z.string().optional().describe(extractFieldsDescription),
    });
  • src/index.ts:265-265 (registration)
    Registration of the list-dashboards tool in the MCP server under the 'discovery' category, with its schema and handler.
    tool("list-dashboards", "List dashboards with pagination and service filtering", listDashboardsSchema.shape, wrapToolHandler(listDashboards));
Behavior2/5

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

With no annotations, the description must convey behavioral traits but only covers basic functionality. Missing details on permissions, rate limits, result format, or handling of pagination limits. The description does not clarify whether the output is a list of IDs or full dashboard objects.

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 sentence that immediately conveys the core purpose without extraneous words. Front-loaded with key actions and features.

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?

The tool has 7 parameters and no output schema, so the description needs to explain return values and all important options. It only mentions pagination and service filtering, ignoring fields, include (deleted/non-deleted), extractFields, and cursor usage. Without annotations, this is insufficient for an agent to use correctly.

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 100% with detailed descriptions for all 7 parameters. The description adds no new parameter info beyond 'pagination' and 'service filtering', which are already evident from the schema. Baseline of 3 is appropriate.

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?

The description clearly states 'List dashboards with pagination and service filtering', specifying the action (list), resource (dashboards), and two key features. This distinguishes it from other list-* tools on the server.

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 is provided on when to use this tool versus alternatives like get-dashboard or other list tools. There is no mention of prerequisites, use cases, or exclusions.

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/us-all/openmetadata-mcp-server'

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