Skip to main content
Glama

edubase_post_organization_webhook

Create a webhook for an organization to automatically receive notifications when users complete exams or quizzes, or test via API.

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?

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context. It does not disclose side effects (e.g., webhook starts delivering notifications), permission requirements, or rate limits. For a creation tool, more transparency is expected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but lacks valuable information. It does not provide an overview or hint at the complexity of the schema. Conciseness is positive but not at the expense of completeness.

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?

Given the tool's complexity (13 parameters, many optional dependencies) and the presence of related CRUD siblings, the description is insufficiently complete. It does not explain the return value (likely the created webhook), nor does it integrate with the broader context of webhook management.

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?

Schema description coverage is 100%, with each parameter having a definition. The tool description adds no additional parameter semantics, so baseline 3 is appropriate. The schema itself provides detailed enum descriptions and field purposes.

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 'Create a webhook for an organization' clearly states the action and resource. It distinguishes from sibling tools like edubase_get_organization_webhook, edubase_patch_organization_webhook, and edubase_delete_organization_webhook. However, it does not explain what a webhook is or differentiate from edubase_post_organization_webhook_trigger, which is a related but distinct action.

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 provides no guidance on when to use this tool versus alternatives (e.g., update via patch or trigger via post). No prerequisites, context, or when-not-to-use information is given, leaving the agent to infer usage from the name alone.

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