Skip to main content
Glama

roles_delete_role_assignment

Remove a role assignment from a user to revoke their role permissions. Requires admin access. Reassign the user to another role.

Instructions

Delete a role assignment.

Removes a role from a user. Requires admin permissions.

Workflow tips:

  • User will lose role permissions

  • User should be assigned to another role

  • Use roles/get_role_assignments to verify removal

Common use cases:

  • Remove role from user: { "id": 123, "user_id": 456 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the role
user_idYesID of the user to remove the role from
Behavior4/5

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

No annotations given; description discloses mutative nature, admin requirement, and consequence (user loses permissions). Suggests using a verification tool. Could mention idempotency or error scenarios.

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 title, description, and tips. Concise but could be slightly tighter. No wasted sentences.

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?

Lacks output schema explanation, error handling details, or synchronization info. Adequate for basic usage but not fully comprehensive.

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%, so baseline is 3. Description adds example usage but no extra semantic depth beyond schema descriptions.

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 action ('Delete a role assignment', 'Removes a role from a user') and distinguishes itself from siblings like roles_add_role_assignment and roles_get_role_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 admin permission requirement and workflow tips (e.g., verify removal), but does not explicitly state when to use vs. alternatives. However, context is clear.

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