Skip to main content
Glama

Get OAuth providers needing production credentials

get_deploy_oauth_providers
Read-onlyIdempotent

List OAuth providers enabled on the development instance, the credential fields each needs in production, and whether production already has them (the OAuth step of clerk deploy).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "get_deploy_oauth_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
providersYes
unsupportedYesEnabled providers whose credential fields could not be described.
production_instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / production_instance_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / production_instance_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "production_instance_id": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "providers": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "config_key": {
      +            "type": "string"
      +          },
      +          "configured": {
      +            "description": "Whether production already has the required credentials.",
      +            "type": "boolean"
      +          },
      +          "fields": {
      +            "items": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "description": {
      +                  "type": "string"
      +                },
      +                "key": {
      +                  "type": "string"
      +                },
      +                "options": {
      +                  "items": {
      +                    "type": "string"
      +                  },
      +                  "type": "array"
      +                },
      +                "type": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "key"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "provider": {
      +            "type": "string"
      +          },
      +          "required_credential_keys": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "provider",
      +          "config_key",
      +          "required_credential_keys",
      +          "fields",
      +          "configured"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "unsupported": {
      +      "description": "Enabled providers whose credential fields could not be described.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "production_instance_id",
      +    "providers",
      +    "unsupported"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed world, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact beyond that: the tool reads from the development instance and cross-references production credential status. It does not discuss auth requirements or behavior when no providers are enabled; a 3 is appropriate given the rich annotation coverage.

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?

One dense but well-structured sentence with the resource front-loaded and the deploy-workflow hook trailing. Every clause carries information (scope, returned fields, production comparison), though the triple-clause construction is slightly packed for a single sentence.

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?

An output schema exists, so the description need not enumerate return values, and annotations cover the safety profile. Combined with 100% parameter coverage, the only minor gap is edge-case behavior (e.g., no OAuth providers enabled), which is not essential to calling the tool correctly.

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?

There is a single parameter (application_id) at 100% schema description coverage, so the schema fully documents its format ('Clerk application ID (app_…)'). The description adds nothing parameter-specific, which is acceptable at this coverage level — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (list OAuth providers) plus the exact scope: providers enabled on the development instance, their production credential fields, and whether production already has them. It is clearly distinct from generic config readers like get_instance_config, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The parenthetical '(the OAuth step of `clerk deploy`)' implies the deploy-preparation workflow where this tool belongs, giving usable when-to-use context. However, it states no explicit exclusions or alternatives (e.g., when to use get_instance_config instead), so the guidance remains implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources