list_webhooksFetches all webhook events for a Teachable school, optionally scoped to a private school profile label, so you can review event activity.
Fetch all webhook events for your school.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Exact private school profile label; not a provider identity or authorization proof. |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the 'for your school' scoping, and says nothing about result size, pagination, or ordering, which is a modest but non-trivial addition given the coverage already present.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence that front-loads the action and resource with zero filler. Nothing could be trimmed without losing meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-optional-parameter list tool with annotations covering safety, this is close to sufficient, but with no output schema the description should at least hint at return shape or volume, and it leaves the overlap with get_webhook_events unexplained. Adequate but with clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single 'account' parameter is already well documented in the schema with a precise definition. The description adds no format, default, or filtering semantics beyond what the schema already states, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb plus resource ('Fetch all webhook events') and scopes it to the caller's school, so the operation itself is unambiguous. However, it makes no attempt to distinguish itself from the sibling tool get_webhook_events, which an agent would have to disambiguate on its own.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus get_webhook_events or any other sibling, and no prerequisites or exclusions are stated. The agent is left to infer usage purely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.