list_webhooksList account webhooks and their study scopes. Signing secrets are never included.
| Name | Required | Description | Default |
|---|---|---|---|
| organization_id | No | Organization for this operation and billing. Use list_organizations to choose an active membership. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | Registered webhooks. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_id / descriptionPrevious value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."Input schema / properties / organization_idAdded value: +{
+ "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / total_count / maximumAdded value: +9007199254740991Output schema / properties / result / properties / total_count / minimumAdded value: +-9007199254740991Output schema / properties / result / properties / webhooks / items / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / webhooks / items / properties / signing_secret / $refRemoved value: -"#/properties/result/properties/webhooks/items/properties/study_id"Output schema / properties / result / properties / webhooks / items / properties / signing_secret / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / webhooks / items / properties / updated_at / $refRemoved value: -"#/properties/result/properties/webhooks/items/properties/created_at"Output schema / properties / result / properties / webhooks / items / properties / updated_at / descriptionAdded value: +"ISO 8601 timestamp."Output schema / properties / result / properties / webhooks / items / properties / updated_at / typeAdded value: +[
+ "string",
+ "null"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds a genuinely useful data detail: signing secrets are never returned. That tells the agent what it cannot retrieve, which is behavior beyond the annotations.
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?
Two terse sentences with the core purpose front-loaded and the security caveat as a clearly subordinate clause. Nothing wasted.
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?
An output schema exists and annotations are rich, so return-value explanation is not needed. The description covers purpose and the secret-exclusion caveat adequately; minor omissions like whether results are paginated or filterable by study are acceptable given the output schema.
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?
The single organization_id parameter is fully documented in the schema (100% coverage), so the schema carries the load. The description's phrase "account webhooks" loosely hints at the account/org scoping but adds no syntax or defaults beyond the schema.
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 and resource (list account webhooks) plus a scope qualifier (their study scopes). It is clearly distinguishable from get_webhook, create_webhook, and list_webhook_deliveries by name and content, though it doesn't explicitly name those siblings.
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?
Usage is implied by "List account webhooks" — an agent can infer this is the enumeration tool — but there is no explicit when-to-use guidance or routing to alternatives such as get_webhook for a single record.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.