Skip to main content
Glama

deactivate_oauth_client

Destructive

Deactivate an OAuth client so it can no longer obtain new tokens. The client record remains with its name, scopes, and history, but appears inactive; existing tokens still expire naturally.

Instructions

Turn an API client off. It can no longer obtain a token.

    `id` is the client's record id from `list_oauth_clients`.

    THIS IS A DEACTIVATION, NOT A DELETION. Skilljar's endpoint is a DELETE verb but
    its own summary calls it "Deactivate client": the record survives, keeps its
    name, scopes and history, and continues to appear in `list_oauth_clients` with
    `is_active` false. Do not report it as deleted.

    Anything using this client stops working at its next token request. A token
    already issued lives until it expires, so deactivating is not instant lockout —
    pair it with `revoke_refresh_token` if you need the access gone now.

    Requires the `clients:write` OAuth scope, and the `admin` capability profile.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
warningNo
client_idNo
is_activeNo
created_atNo
descriptionNo
ip_allowlistNo
client_secretNo
scope_codenamesNo
Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), the description discloses crucial behavior: the endpoint uses a DELETE verb but is semantically a deactivation, the record survives with is_active false, already-issued tokens live until expiry, and the required OAuth scope and capability profile. This adds significant context that annotations alone do not provide.

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 detailed but every sentence earns its place: core action first, id source second, the critical deactivation-vs-deletion warning, token behavior, companion tool, and permissions. The all-caps warning is justified by the DELETE-verb confusion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with gotchas, the description covers all necessary context: id provenance, non-deletion semantics, effect on current tokens, companion for immediate lockout, and auth requirements. Since an output schema exists, return value details are unnecessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 0%, the description fully explains the only parameter: 'id is the client's record id from list_oauth_clients.' This gives the agent exact sourcing instructions that the schema (just type: string) does not.

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 states a specific verb-resource pair: 'Turn an API client off. It can no longer obtain a token.' It explicitly distinguishes deactivation from deletion, and names the source of the id, making the tool's purpose unambiguous among OAuth client siblings like update_oauth_client and revoke_refresh_token.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use and when-not-to-use guidance: it warns not to report the operation as deletion, and instructs pairing with revoke_refresh_token when immediate access termination is needed. This clearly routes an agent to the correct alternative for a different need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/CloudSecurityAlliance/csa-skilljar'

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