LearningSuite MCP Server

learningsuite_create_webhook_subscription

Create a webhook subscription to receive notifications for LearningSuite events. Specify the target URL, event types, and secret to start receiving automated updates.

Instructions

Create a webhook subscription

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": {
      "url": "<url>",
      "events": "<events>"
    },
    "name": "learningsuite_create_webhook_subscription"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Webhook URL
`events`	Yes	Array of event types to subscribe to
`secret`	No	Webhook secret

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3/5.0

Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It merely states 'Create a webhook subscription' with no information about side effects, required authentication, validation rules, or what happens on success/failure. This is a bare tautology with no additional behavioral disclosure.

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 a single short sentence with no redundant words, front-loading the core action and object. It is optimally concise, though it could be expanded with contextual details.

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

Completeness2/5

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

For a create operation with no output schema and no annotations, the description is insufficiently complete. It doesn't explain what a webhook subscription is, what events will trigger it, or any response details. The agent would need to rely on schema property names (url, events, secret) and sibling tool names to infer context.

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?

All three parameters (url, events, secret) have schema descriptions, so schema coverage is 100%. The description adds no parameter-level semantics beyond what the schema already provides, so the baseline of 3 applies.

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 uses a specific verb ('Create') with a specific resource ('webhook subscription'), clearly distinguishing it from sibling tools like update/delete/list/get webhook subscriptions. The verb-resource structure is unambiguous and matches the tool name.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool, prerequisites, or alternatives. There is no mention of how this relates to other webhook subscription tools or what event types are supported. The agent must infer usage from the tool name alone.

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

Deploy Server