Skip to main content
Glama

roles_list_role_pipelines

List all pipelines and their visibility status for a specific role. Use to audit which pipelines are visible or hidden for a role.

Instructions

List pipeline visibility for a role.

Returns all pipelines and their visibility status for a specific role. For more information on pipeline visibility, please refer to the Visibility groups article.

Workflow tips:

  • Shows which pipelines are visible/hidden for the role

  • Use visible parameter to filter only visible pipelines

  • Useful for managing pipeline access by role

  • Cached for 15 minutes

Common use cases:

  • List all pipelines for role: { "id": 123 }

  • List only visible pipelines: { "id": 123, "visible": true }

  • Audit pipeline visibility settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the role
visibleNoWhether to fetch only visible pipelines
Behavior4/5

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

The description mentions a 15-minute cache, which is important for agents to know about data freshness. No annotations are provided, so the description carries the burden for behavioral traits. It does not contradict any annotations.

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?

The description is well-structured with a clear purpose statement, followed by workflow tips and common use cases. It is concise, front-loaded, and each sentence adds value without redundancy.

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?

The description explains the return type (all pipelines with visibility status) and caching behavior. It does not detail the exact structure of the response, but for a list tool, this is sufficient given no output schema.

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?

Both parameters have schema descriptions, and the description reinforces their use with examples, such as filtering by 'visible'. This adds practical guidance beyond the schema definitions.

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 'pipeline visibility for a role'. It specifies the scope (specific role) and distinguishes from sibling tools like roles_get or roles_update_role_pipelines, which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides workflow tips and common use cases, including how to use the 'visible' parameter for filtering. However, it does not explicitly state when not to use this tool or compare with alternatives like roles_get_role_assignments.

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/iamsamuelfraga/mcp-pipedrive'

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