Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-pipelines

Retrieve a paginated list of pipelines, filterable by service and configurable fields, to access pipeline metadata.

Instructions

List pipelines with pagination and service filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include (e.g. 'owners,tags,followers,tasks')
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

  • Handler function that executes the list-pipelines tool. Makes a GET request to /pipelines with the provided parameters (fields, limit, before, after, service, include, extractFields).
    export async function listPipelines(params: z.infer<typeof listPipelinesSchema>) {
      return omClient.get("/pipelines", params);
    }
  • Zod schema definition for list-pipelines input parameters: fields, limit (default 10), before/after cursors, service filter, include (default 'non-deleted'), and extractFields.
    export const listPipelinesSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include (e.g. 'owners,tags,followers,tasks')"),
      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: ef,
    });
  • src/index.ts:274-274 (registration)
    Registration of the 'list-pipelines' tool with the MCP server using the schema shape and wrapped handler.
    tool("list-pipelines", "List pipelines with pagination and service filtering", listPipelinesSchema.shape, wrapToolHandler(listPipelines));
  • The wrapToolHandler helper that wraps the handler with error handling and redaction logic (used by the registration).
    export const wrapToolHandler = createWrapToolHandler({
      redactionPatterns: [/OPENMETADATA_TOKEN/i],
      errorExtractors: [
        {
          match: (error) => error instanceof WriteBlockedError,
Behavior2/5

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

With no annotations, the description should disclose behavioral traits, but it only mentions basic features. It does not state that the operation is read-only, the return format, or any limitations.

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 very short (6 words) and front-loaded, but could benefit from slightly more structure or detail without becoming verbose.

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?

Given 7 parameters with no output schema, the description is insufficient. It does not explain pagination cursors, fields, extractFields, or include options, leaving the agent underinformed.

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 all parameters described. The description adds 'pagination and service filtering', which is already evident from the schema. Baseline 3 applies as no additional value.

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 the verb 'list' and the resource 'pipelines', and adds pagination and service filtering, distinguishing it from other list tools in the sibling list.

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 list-tables or list-queries. There is no mention of context or preconditions.

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