Skip to main content
Glama

permission_sets_list

List all permission sets in your company, detailing configurations for admin, regular, and custom sets across apps. Filter by sales, global, or account_settings.

Instructions

List all permission sets within the company.

Returns all permission sets with their configurations, including admin and regular user sets across different apps.

Workflow tips:

  • Permission sets define user access and capabilities

  • Apps include: sales, global, account_settings

  • Each set has a type (admin, regular, custom)

  • Shows assignment counts for each set

  • Cached for 15 minutes (permission sets rarely change)

Common use cases:

  • List all permission sets: {}

  • Filter by app: { "app": "sales" }

  • View global permissions: { "app": "global" }

  • Check account settings access: { "app": "account_settings" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoThe app to filter the permission sets by (e.g., sales, global, account_settings)
Behavior4/5

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

Despite no annotations, the description discloses caching behavior (15-minute cache) and implies a read-only operation; no contradictions.

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?

Well-structured with bullet points and examples, though slightly verbose; front-loaded with the main purpose.

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?

Describes return content (configurations, assignment counts) sufficiently for a list tool with no output schema; covers key aspects.

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?

Schema covers the parameter with examples, and the description adds value by showing common use cases and filter context, though schema coverage is 100%.

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 all permission sets within the company' and specifies the returned information, distinguishing it from sibling tools like permission_sets_get and permission_sets_get_assignments.

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?

Provides workflow tips and common use cases with example filters, but does not explicitly mention when to use alternatives like permission_sets_get.

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