list_webhooksList account webhooks and their study scopes. Signing secrets are never included.
| Name | Required | Description | Default |
|---|---|---|---|
| organization_id | No | Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | Registered webhooks. |
Changes observed during successful MCP inspections.
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 readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety and idempotency are covered. The description adds valuable context beyond annotations: it notes that signing secrets are never included, which is important for security and data handling. It also clarifies that study scopes are returned. This goes beyond what annotations provide, though it doesn't discuss pagination or rate limits.
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 concise sentences that are front-loaded with the main action and a critical detail. Every word earns its place, with no redundancy or filler.
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 list operation with a single optional parameter, an output schema, and rich annotations, the description is nearly complete. It covers the scope of results and an important exclusion (signing secrets). However, it could mention whether results are paginated or filtered by default, which might be relevant given the openWorldHint.
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 coverage is 100%, and the single parameter (organization_id) is fully documented in the schema with details about platform admins and required conditions. The description adds no parameter-specific information, which is acceptable given the high schema coverage. Baseline 3 is appropriate.
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 clear verb+resource: 'List account webhooks', which distinguishes it from get_webhook, create_webhook, and delete_webhook. It also mentions 'study scopes' and adds a scope note about signing secrets. However, it doesn't explicitly differentiate itself from siblings like list_webhook_deliveries, which an agent might confuse with a listing operation.
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?
No guidance on when to use this tool versus alternatives such as get_webhook or list_webhook_deliveries. There is no mention of prerequisites, conditions, or exclusions. The description only says what it does, not when it should be used.
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.