Skip to main content
Glama

edubase_post_organization_webhook

Create webhooks to receive real-time notifications when users complete exams or quizzes in your organization. Configure endpoints, trigger events, and authentication to automate result processing and system integrations.

Instructions

Create a webhook for an organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesorganization identification string
nameYestitle of the webhook
trigger_eventYesType of event to trigger webhook: - exam-play-result: triggers when a user (must be member of the organization) completes an exam in the organization - quiz-play-result: triggers when a user (must be member of the organization) completes a quiz in practice mode in the organization - api: triggers when a manual API call is made (useful for testing and debugging)
endpointYesURL to send webhook notifications to
methodNoHTTP method to use for webhook notifications (default: POST) - POST - GET
authenticationNoType of authentication (default: none): - none: no authentication - key: use a secret key (or password) for authentication
authentication_sendNoHow to send authentication data (default: data): - header: as header field - bearer: as Bearer token in Authorization header - data: as data field (in body or query string)
authentication_send_headerNoname of header field to send authentication data in, required if authentication is set to key and authentication_send is set to header
authentication_send_dataNoname of data field to send authentication data in, required if authentication is set to key and authentication_send is set to data
authentication_keyNosecret key (or password) to use for authentication, required if authentication is set to key
authentication_key_customNocustom field name to use as the authentication key, required if authentication is set to key, mutually exclusive with authentication_key
extra_dataNoadditional data (as JSON encoded string) to send with the webhook notification
retryNoHow to retry webhook notifications on failure (default: error): - none: no retry - error: delayed retry on any error

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesorganization identification string
webhookYeswebhook identification string
Behavior2/5

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

While annotations indicate this is a non-idempotent write operation (readOnlyHint=false, idempotentHint=false), the description adds no behavioral context about side effects, failure modes, or the persistent nature of the created webhook versus transient triggers.

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?

The single-sentence description is efficiently structured with no redundancy. However, given the tool's complexity (13 parameters with intricate authentication options), extreme brevity may underserve the agent's understanding.

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 tool with 13 parameters supporting multiple authentication schemes (key, bearer, header, data) and three distinct trigger types, the 5-word description is insufficient. It omits critical context about the webhook's persistent nature and the complex authentication configuration required.

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?

With 100% schema description coverage including detailed enum explanations for trigger_event and authentication flows, the schema carries the full burden of parameter documentation. The description adds no parameter guidance, which is acceptable given the comprehensive schema.

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?

The description uses a specific verb ('Create') with clear resource ('webhook') and scope ('organization'). However, it fails to distinguish from the sibling tool 'edubase_post_organization_webhook_trigger', which manually triggers webhooks rather than creating persistent configurations.

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?

No guidance provided on when to use this creation tool versus the patch variant for updates, or prerequisites like required permissions. The idempotentHint=false annotation suggests multiple calls create multiple webhooks, but the description doesn't warn about this behavior.

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/EduBase/MCP'

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