Skip to main content
Glama

roles_update_role_pipelines

Update pipeline visibility for a role by setting specific pipelines as visible or hidden using a mapping of pipeline IDs to 1 (visible) or 0 (hidden).

Instructions

Update pipeline visibility for a role.

Updates the specified pipelines to be visible and/or hidden for a specific role. For more information on pipeline visibility, please refer to the Visibility groups article.

Workflow tips:

  • Use object with pipeline IDs as keys and 1/0 as values

  • 1 = visible, 0 = hidden

  • Requires admin permissions

  • Changes affect all users with this role

  • Use roles/list_role_pipelines to see current visibility

Common use cases:

  • Make pipelines visible: { "id": 123, "visible_pipeline_ids": { "1": 1, "2": 1 } }

  • Hide specific pipelines: { "id": 123, "visible_pipeline_ids": { "3": 0 } }

  • Mix visibility: { "id": 123, "visible_pipeline_ids": { "1": 1, "2": 0 } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the role
visible_pipeline_idsYesObject where keys are pipeline IDs and values are 1 (visible) or 0 (hidden)
Behavior4/5

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

With no annotations provided, the description adequately discloses key behavioral traits: requires admin permissions, changes affect all users with the role, and the format for setting visibility. It also references an article for more information. However, it doesn't detail error handling or whether the update is incremental or full replacement.

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 main statement, workflow tips, and common use cases. Every sentence adds value, and there is no redundant information. It is concise yet comprehensive.

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?

While the description covers the input and effect well, it does not explain the output or return value of the tool. Since there is no output schema, the agent would benefit from knowing what the response contains (e.g., success confirmation, updated role object). This omission leaves some contextual gaps.

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?

The input schema provides descriptions for both parameters (id and visible_pipeline_ids), achieving 100% coverage. The description adds value by giving examples of valid values (1 for visible, 0 for hidden) and demonstrating usage patterns with common use cases. This goes beyond the schema's basic explanation.

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 and resource: 'Update pipeline visibility for a role.' It specifies that it updates visible/hidden status for pipelines and references the sibling tool 'roles/list_role_pipelines' for current visibility, distinguishing it from related tools.

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 includes workflow tips on the object format (keys as pipeline IDs, values 1/0), requires admin permissions, and notes that changes affect all users. It also suggests using 'roles/list_role_pipelines' to see current visibility. However, it doesn't explicitly state when not to use this tool or provide alternative tools for other use cases.

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