Skip to main content
Glama

products_list_permitted_users

Retrieve a list of users with permission to view and edit a specific product based on its visibility settings. Useful for auditing access and troubleshooting why a user cannot see a product.

Instructions

List all users who have access to view and edit a specific product.

Returns a list of users who have permission to access this product based on visibility settings and team structure.

Workflow tips:

  • Product visibility determines which users can access it

  • Visibility can be: owner only, owner's team, entire company, or custom

  • This is useful for understanding who can see and modify the product

  • Access permissions affect whether users can add the product to deals

Common use cases:

  • Audit product access permissions

  • Verify team members can see a product

  • Check visibility before sharing product with team

  • Troubleshoot why a user cannot see a product

Example: { "id": 123 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID
Behavior4/5

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

No annotations are provided, so the description carries the burden. It explains that the tool returns users based on visibility settings and team structure, and describes visibility options (owner only, team, company, custom). It also notes that access permissions affect product addition to deals. This provides good behavioral context beyond the schema, though it does not explicitly state read-only nature, which is implied by 'list'.

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 well-structured with a clear first sentence, then workflow tips, common use cases, and an example. Every sentence adds value, though it could be slightly more concise. Front-loaded with purpose.

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?

With one parameter and no output schema, the description explains the return concept and visibility logic, and includes an example. However, it does not specify the structure of returned users or address pagination/errors. Adequate but with gaps.

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 one parameter (id) described as 'Product ID'. The description does not add additional meaning or constraints beyond what the schema provides. Per guidelines, baseline 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 explicitly states the tool lists users with view/edit access to a specific product. The verb 'list' and resource 'users permitted for product' are clear, and the tool name includes 'products' to differentiate from sibling list_permitted_users tools for deals, organizations, and persons.

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 (audit, verify, troubleshoot) that help an agent decide when to use this tool. However, it does not explicitly state when not to use it or compare with alternatives like other list_permitted_users tools.

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