Skip to main content
Glama

list_webhooks

Read-onlyIdempotent

List webhook subscriptions to reveal where Skilljar sends events, the event types that trigger them, and whether each is active or deactivated after delivery failures. Credential values are withheld.

Instructions

List webhook subscriptions - where Skilljar sends events, and on what.

    SECRETS ARE WITHHELD. Skilljar returns a shared-secret header value, any token in
    the target URL's query string, and a Basic-auth password in plain text. None of
    those are returned here. You get the header NAMES, and the URL's host and path,
    which answer where an event goes without handing over the credential.

    `event_type` is what fires it - `preview_event_payload` shows the shape of that
    event's body. `active` false with a `deactivate_reason` usually means Skilljar
    turned it off after repeated delivery failures, which is worth reporting: a
    webhook can be configured correctly and still be dead.

    To see a secret, read it in the Skilljar Dashboard. It is deliberately not
    available through this server.

    Requires `CSA_SKILLJAR_V1_API_KEY`, a separate credential from the v2 client.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
pageNo
rowsYes
totalNo
has_moreNo
next_pageNo
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses crucial behavior: secrets are withheld, only header names and URL host/path are returned, active=false with deactivate_reason usually indicates delivery failures, and a separate v1 API key is required. This is exactly the kind of non-obvious behavior an agent needs to know.

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 front-loaded with the core purpose and then adds only high-value caveats: secret handling, active/deactivate_reason semantics, Dashboard alternative, and credential requirement. Every section earns its place without redundant filler.

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 list operation, the description covers what is returned, what is deliberately excluded, how to interpret important fields, where to go for secrets, and which credential is required. The output schema is present, so the description does not need to enumerate return values, and pagination parameters are adequately represented in the schema.

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

Parameters2/5

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

The input schema has only page and page_size with no descriptions, and the description does not explain their meaning, formatting, or relationship. While the names are self-explanatory, the description provides zero guidance on pagination behavior, limits, or defaults, and schema coverage is 0%.

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 opens with a specific verb and resource: 'List webhook subscriptions - where Skilljar sends events, and on what.' This clearly identifies the operation and differentiates it from related tools like get_webhook and preview_event_payload by focusing on the list-level subscription details.

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 strong context for when to use this tool, including credential requirements and the fact that secrets are deliberately unavailable. It also gives an explicit alternative path for viewing secrets ('read it in the Skilljar Dashboard'), but it does not explicitly mention when to prefer get_webhook over this list endpoint.

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